Hi all. It's me again. Sorry about the silly, whimsical post earlier. I actually have a legitimate question now... I'm on Chapter 6 installing Glibc again.... Even this seems like a silly question but I feel the need to ask it anyway.... Why do I have to remove the folder "glibc-2.3.2" and unpack it again when I never built in that directory initially? This doesn't make any sense to me. The same with binutils.... I removed "binutils-2.1.4" and "binutils-build" because the book specifically told me to do so, but again, why? I didn't build in binutils-2.1.4 so why remove it and unpack again when it is already clean? I can see why you would want to remove the build directory but not the source... Everything should be linked against /tools and nowhere else, right? So... I have an already clean glibc folder that has the extracted linuxthreads and is already patched..... I honestly feel like ignoring the directions and continuing... Any problem with this that I'm just not seeing? Thank you all for your anticipated input....

Jon

Well, I'm not on Chapter 6 yet, but maybe my error with Installing GCC-3.3.1 - Pass 2 will help, quote from bookI had stuck these in the GCC 3.3.1 directory from pass 1............when I got down to this I got an error that configure could not find C++
the msg said config could only find-- C treelang
So I deleted both directories and started it again, everything came out OK, and I was able to continue on with--make
So the moral is that pass 1 left some stuff in the directory that was un-usable or un-needed by pass 2, so a new and clean environment was needed to start over with.

Right... I've noticed where it tells you to remove the source and build directories on certain occassions. Other times it will tell you to keep the build around for later use. Thats cool and straight forward but most of the time it doesn't tell you to remove the source directory but then later it's telling you to unpack it again.. I've had to do an awful lot of deciphering/judgement calls with this book on when and when not to mess with stuff. Thats alright I guess. I guess I'll just have to work it a few times thru trial and error and see what I can figure out... No biggie. Guess I was just expecting the book to hold your hand the whole time which it does but doesn't do at the same time... Just seems a little obscure here and there on "simple" stuff, which tends to make me second guess things.... Whether the obscurity that I see was intentional or not, I don't know. Oh well....

Jon