Before I get started: yes, I've read the GCC-FAQ, various other HOWTOS and
FAQS, READMES and a couple of linux books. And I'm actually more concerned
about the libc libraries.
I installed linux on my PC because I wanted to learn and to have some fun.
Yesterday, out of sheer boredom, I decided to upgrade from gcc 2.5.8 to gcc
2.6.2. From sunsite I picked up:
and the appropriate release.* files.
I followed all of the directions in the release files and then I decided to
compile the libc package myself. I compiled the tools archive using my
newly installed gcc-2.6.2. I then unarchived the libc package and did the
Beforehand I also ran a make configure in my /usr/src/linux directory. To
play it safe I redirected stderr and stdout to separate files before I
started the compile and then went to bed. When I got up this morning I
found the stderr file to contain 3500+ lines. This doesn't sound right to
me! I ran a grep -vi 'warning' on the file because I figured warnings
weren't of much concern. As it turns out only about 750 lines aren't
directly warning related.
Point is: I have a WHOLE LOT of errors along the line of "File Not Found".
That doesn't sound right. I can overlook a few errors granted but 3500 or
even 750 is still enough to worry me.
Does anyone know if I'm doing something wrong? I would be happy to email
the stderr file to anyone who would be willing to help. I'd post it, but
you get the idea about the file size. I would REALLY like to reduce the
number of errors here. I'm afraid I'm a newbie to C programming (although
not to programming in general) and I don't want to have to mess with the
source too much.
Any help or suggestions would be appreciated.
Incidentally, gcc seems to run fine. It's just these libraries I'm concerned
Alan Wild "Speed News Guy" WWW:http://www.spd.louisville.edu/~arwild01/