Re: 1.9.1 and glibc 2.0.1

Eric Youngdale (
Tue, 1 Apr 1997 00:02:14 -0500

>Third, I look at your problem but I have no clue how this can ever be
>possible. Nobody reported something similar and compiling glibc
>several hundred of times myself never showed this as well. I guess
>it's a broken installed gcc.

Umm, time out guys. This is *exactly* the same problem that I
was having. The problem was due to the fact that the autoconfigure
didn't correctly detect that linker flag --no-whole-archive was supported
in my linker. In my case it was because I had run ./configure with bogus
CFLAGS, and the test failed.

One thing that is particularly annoying about this problem is that
once this is misdetected, running configure again won't fix it unless you
first delete config.cache.

Come to think of it, I don't believe that glibc will compile out of
the box if your linker doesn't support this switch.