This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[PATCH,4.3,committed] Re: GCC 4.3.4 release candidate available
- From: Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- To: GCC Patches <gcc-patches at gcc dot gnu dot org>
- Cc: Kai Tietz <ktietz70 at googlemail dot com>, Richard Guenther <rguenther at suse dot de>, Dave Korn <dave dot korn dot cygwin at googlemail dot com>
- Date: Wed, 29 Jul 2009 12:58:47 +0100
- Subject: [PATCH,4.3,committed] Re: GCC 4.3.4 release candidate available
- References: <alpine.LNX.2.00.0907271811000.16347@zhemvz.fhfr.qr> <4A70185F.8050402@gmail.com> <alpine.LNX.2.00.0907291139230.16347@zhemvz.fhfr.qr> <90baa01f0907290241o1d7e8e55u66a2be2779587fcb@mail.gmail.com>
Kai Tietz wrote:
> 2009/7/29 Richard Guenther:
>> On Wed, 29 Jul 2009, Dave Korn wrote:
>>
>>> Richard Guenther wrote:
>>>> A release candidate for the GCC 4.3.4 is now available at
>>>>
>>>> ftp://gcc.gnu.org/pub/gcc/snapshots/4.3.4-RC-20090727
>>>>
>>>> I plan to roll out the final release at the beginning of next week
>>>> if there are no major problems reported.
>>> Bootstrap failure on Cygwin:
>>> This is PR 38903. Can we backport the fix? (I'm just testing it against the
>>> RC tarball right now.)
>> Yes, if this is ok with the Cygwin maintainers.
>>
>> Thanks,
>> Richard.
>>
>
> It is fine.
>
> Thanks,
> Kai
Thanks guys. Bootstrapping the RC with the patch applied completed OK so I
checked it in.
PR bootstrap/38903: Backport fix from HEAD.
* configure.ac (funcs, vars, checkfuncs): Don't munge on Cygwin,
as it no longer shares libiberty object files.
* configure: Regenerated.
Test results to follow, after the usual 3-4 day wait...
cheers,
DaveK
Index: libiberty/configure.ac
===================================================================
--- libiberty/configure.ac (revision 150203)
+++ libiberty/configure.ac (working copy)
@@ -571,29 +571,6 @@
case "${host}" in
- *-*-cygwin*)
- # The Cygwin library actually uses a couple of files from
- # libiberty when it is built. If we are building a native
- # Cygwin, and we run the tests, we will appear to have these
- # files. However, when we go on to build winsup, we will wind up
- # with a library which does not have the files, since they should
- # have come from libiberty.
-
- # We handle this by removing the functions the winsup library
- # provides from our shell variables, so that they appear to be
- # missing.
-
- # DJ - only if we're *building* cygwin, not just building *with* cygwin
-
- if test -n "${with_target_subdir}"
- then
- funcs="`echo $funcs | sed -e 's/random//'`"
- AC_LIBOBJ([random])
- vars="`echo $vars | sed -e 's/sys_siglist//'`"
- checkfuncs="`echo $checkfuncs | sed -e 's/strsignal//' -e 's/psignal//'`"
- fi
- ;;
-
*-*-mingw32*)
# Under mingw32, sys_nerr and sys_errlist exist, but they are
# macros, so the test below won't find them.