Re: glibc 2.3.1 borked

[Andreas Jaeger]

<address@hidden> writes:

> dear programmers. i am sitting here on a halfbroken system right now and i am 
> terrible upset and pissed off because of the bad quality in your releases.
> i downloaded glibc 2.3.1 today and compiled it as usual (it is not the first 
> time that i compile glibc or gcc on my own) and today
> i figured out that glibc 2.3.1 is as usual fucked up. i can't understand why 
> you people release things without proper testing.
> look i compiled glibc 2.3.1, run the check and installed it. so far 
> everything works perfectly. i bet thats all you folks did too and after this 
> you simply threw out the shit without proper verification that other programs 
> namely 'gcc-3.2' could be re-compiled with that shit.
> try to install glibc-2.3.1 on a normal intel platfrom by using ./configure 
> --prefix=/usr && make && make install. then try to re-compile the official 
> 3.2 release of gcc with ./configure --prefix=/usr && make bootstrap. the 
> compile fails in the libstdc++-v3 in the locale.cc file. i mean i respect all 
> your hard work on making gnu tools so powerful but you really need to proper 
> check the stuff before releasing it.
> i mean it makes no real sense to release a new glibc-2.3.1 which is not able 
> to compile at least gcc-3.2 afterwards. i would really be thankful if you 
> make sure for the future that at least major things like linux kernel and gcc 
> could be compiled with it.

Read the glibc FAQ, we documented the problem before releasing glibc 2.3: 

2.37.   When recompiling GCC, I get compilation errors in libstdc++.


Andreas
-- 
 Andreas Jaeger
  SuSE Labs address@hidden
   private address@hidden
    http://www.suse.de/~aj