> Hi! This is not really kernel related, but I was hoping enough folks
> around here knew enough about the guts of gcc and the linker to offer me
> some insight...
>
> I compiled glibc the other day and neglected to tell it to install in
> /lib, so it stuck itself in /usr/local/lib. If I explicitly tell gcc to
> look in /usr/local/lib, it finds glibc and its linker, otherwise it finds
> the linker (Which I explicitly defined in
> /usr/lib/gcc-lib/i586-pc-linux-gnulibc1/specs) but it can't find glibc.
> Anyone know how to force gcc to always search in /usr/local/lib while
> linking?
You probably don't want to do that. I'm just guessing, but I bet the
include files wound up in /usr/local/include, and generally made a big
mess. I'd suggest removing it manually and reconfiguring the thing with
'--prefix=/usr'.
On a related note, does anyone have any idea why glibc takes so long to
compile? I figure it has something to do with the amount of time spent in
make, but I don't know how to get hard numbers on that.