This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Large increase in testsuite failures in optimized 3.0 20010613 (prerelease)
- To: ronis at onsager dot chem dot mcgill dot ca
- Subject: Re: Large increase in testsuite failures in optimized 3.0 20010613 (prerelease)
- From: Andreas Jaeger <aj at suse dot de>
- Date: 14 Jun 2001 22:21:50 +0200
- Cc: gcc-bugs at gcc dot gnu dot org
- References: <15144.56452.74863.281862@ronispc.chem.mcgill.ca>
David Ronis <ronis@ronispc.chem.mcgill.ca> writes:
> Alexandre Oliva wrote:
>
>>On Jun 14, 2001, David Ronis <ronis@ronispc.chem.mcgill.ca> wrote:
>
>>> /usr/i686-pc-linux-gnu/bin/ld: warning: libgcc_s.so.0, needed by /usr/lib/gcc-li
>>> b/i686-pc-linux-gnu/3.0/../../../libm.so, may conflict with libgcc_s.so.1
>
>>Did you really build glibc against the unstable libgcc? I'm afraid
>>you'll have to rebuild it.
>
> Thanks for the reply. Yes, dumb as it sounds, I did (inorder to get
> stack alignment to work). On the other hand, this was done long ago
> and nothing has changed since (I'm still using glibc-2.2.2, and was
> planning to 2.2.3 soon).
>
> Why did the failures just turn up? Moreover, is the current snapshot
> stable enough to build 2.2.3?
It should be stable enough - but I don't do it. Glibc and GCC are out
of synch since the latest exception handling and compiling glibc with
the currrent GCC will cause lots of problems. We have to find a way
to fix this (will need fixes in glibc but might also need fixes in
GCC). I advise to wait for glibc 2.2.4,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj