The first barrier..

I've gotten up to compiling glibc-2.2.4 and struck a small problem..

when trying to compile I get the error :


checking whether the C compiler (gcc ) works... \c
no
checking whether the C compiler (gcc ) is a cross-compiler... \c
(cached) \c
yes
checking whether we are using GNU C... \c
no
configure: error: GNU libc must be compiled using GNU CC
<s-packages-3.1/glibc-build#
I assume its cause glibc isn't installed to start with, so I'm thinking I should be doing it via root in my redhat distro

what have I done wrong?? or not done at all??

and whats with the \c at the end of every line? I didn't see that in other peoples post?

So if I tried to compile it as root of my distro it would work right?
I was gonna try it but didn't wanna break anything..that and the book says no..

(weird how many questions you can have off a simple error eh)

also..the booklet thing states its glibc-2.2.5 when the package is 2.2.4..
I change the script to reflect that cause I doubted it was gonna work if I didn't...but pretty sure you guys have seen the typo already (was it a typo?)

You are using version 3.1 of the book right? I don't see glibc-2.2.5 anywhere in my book it's all 2.2.4.
You should compile it when chrooted into your lfs system. You don't have to be root in your host distribution to compile it like you did the previous packages.
I've never seen any of those \c when I was building it. You might want to go back a few steps and confirm that every packages has been properly installed. Especially since your first error states that the c compiler doesn't even work. You kinda need it to continue the rest.

Hey ya know your right, the pdf file I downloaded at home says 2.2.5 and the one at work say 2.2.4..weird..
I should be able to look at all the dir's and that would tell me if I've left anything out..
Cause I thought maybe it was gcc so I reinstalled that just in case I was going senile but no difference..I know its my fault since no one else had this issue but I'm not sure what I could have missed.. I've been doing it without scrips or anything so possibly I've made a typo somewhere along the line..
I've also tried :
screaming
cursing
throwing things at it
threatening it with death
threating to like windows better
pleading with it..
singing to it..
Offering it alcohol..
Offering it weed..
Offering marrage..
Offering a prostitute..male and female..
Offering to buy it a car..
promising to not kiss girlfriend in front of it..
Threating to cut the power cable..
Offering food..
Offering chocolate..
Promising not to press the reset button again..
Promising not to overclock it..
and I even promissed I wouldn't let anyone under the age of 10 play on it ever again..

alas still not reaction..

have you tried setting the execute permissions on gcc and the making sure it's in the right path?

I haven't verified where it is nor permissions..if the permissions are wrong it would tell me in the compile right? according to docs it went into /mnt/lfs/usr .. But I have a look after work and stop assuming..
Thanks..

You got some problems.

first of all, the \c indicates that something is missing. I can't quite remember what causes a missing \c but I do remember that by inspecting the configure output right from the very beginning will tell you that something is missing. Look for "no such file or directory" errors.

Secondly, it not being able to detect whether or not you're using GNU CC is most often caused by /mnt/lfs/usr/bin/egrep missing, or not being statically linked. Either way, you're going to have to exit chroot, go back to chapter 5 and reinstall grep.

May I point you to http://search.linuxfromscratch.org and http://www.linuxfromscratch.org/faq/

Both problems occur quite frequently and the GNU CC thing is so frequent it even made it in the FAQ.

I think it's safe to say at this point that there's no single error encountered during LFS compile jobs that hasn't been encountered before, so the search engine (that searches the mailing list archives) is your friend.

Thankyou muchly, I'll read through the configure output properly and find out what I have or haven't done..
and I'l read the faq now to stop silly questions in future

yep you were right, I reinstalled it and all is well again..cheer cheer..