Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It never makes it past this part no matter how I go about getting there. I have searched google and there is absolutely no information thats relevant to me about how to fix this problem.
Can anyone point me in a direction, preferably the right one?
I was using the live CD when I got this error. The funny part about this is no matter which HOST system I use or which ever version of the CD/Book I use I can never EVER complete the gcc build. I always fail on the GCC build. Can someone for the love of whatever, fix my problem???
I am now getting frustrated with this whole process because there is no information gcc compile errors.
Only thing google tells me is, its a hardware issue. Well, I beg to differ, because all this hardware has been proven to work perfectly since I hand picked it 2 months ago.
Last edited by havenoidea; 11-10-2007 at 08:25 AM.
Saying that you have proven your hardware to work perfectly since you hand picked it is a cop-out. What have you actually done to prove that your hardware was not at fault? Did you check your CPU temps while you were compiling?
Saying that you have proven your hardware to work perfectly since you hand picked it is a cop-out. What have you actually done to prove that your hardware was not at fault? Did you check your CPU temps while you were compiling?
temps are 36C CPU and 26C MOBOPU and I memtested the memory 2 hours with NO errors. Now do you wanna tell me again that I cop'd out?
thanks for at least having an opinion. Now what the hell can this be?
keeps forcing me to a hardware problem, but the bios is set by SPD. Memtest86 comes back clean as a whistle and everything else I have ever tried works on this system except for this compiling GCC error.
I am even using the generic ubuntu kernel for 64 bit. Beyond using a new computer I can't really change much... This is so frustrating yet so sad...
In your results, this line brought back some memories of my own, compiling gcc ? version:
/bin/sh ../../gcc-4.1.1/gcc/../move-if-change tmp-attrtab.c insn-attrtab.c
echo timestamp > s-attrtab
This is a loop in the source code, which passes over the section three times.
I eventually picked up and got through to the finish line. Took two continuations
after the failed start. Sorry, I do not remember what changes I made, but I had
to add two links to make it work.
One thing I noticed about your most recent post was that it appears that different
gcc versions are being amalgumated into one pool. I think you need to find a way
to use only the same compiler version to work your way over the source.
From your backtrace, 4.1.3:
/usr/lib/gcc/x86_64-linux-gnu/4.1.3/cc1[0x56b762]
From your command line reproduced in the second line above: 4.1.1
Do not expect to succeed with mixed versions of the compiler.
One thing I noticed about your most recent post was that it appears that different
gcc versions are being amalgumated into one pool. I think you need to find a way
to use only the same compiler version to work your way over the source.
I'd like to know as well, because from what I can tell I didn't install no 4.1.3. I have 4.1.1 d/l'd and thats what I am trying to install as my compiler for compiling LFS, but my host system uses gcc 4.1.2.
4.1.3 seems odd indeed, because I am not sure where its coming from???
This is really frustrating, I am completely stumped. I have checked my memory without failure, I have just updated the newest bios version thinking my NF4 chipset was the problem(still may be, but firmware is up to date)but thats updated now as well and I still get the same error.
I am wondering now if I should just start over and re-compile binutils, its the only thing I compiled and the only thing I compiled with the old bios settings and bios firmware. I am no guru I don't even know if this will work???
edit: compiled again this time with no backtrace, sorta like the first post. Just weird how each time it has a different way of erroring but still with the same error. Sounds hardware, but what sort of problem because everything else seems to have no problems running on this machine. I even installed and compiled gcc-4.1.1 with the minimal gentoo liveCD.
Just shoot me now.
Last edited by havenoidea; 11-10-2007 at 08:58 PM.
I made it a little further by following a guide on ubuntu forums on compiling gcc 4.2.2 with optimized flags. Now I get this, but the good part is it right through the above part on both the 2 previous passes. This is very good news.
Now what does this mean ^^^^. I looked it up on google and it seems all i get is old patches because 'patch' just complains that it assume -R (reverse) but I said no and now none of the patches work.
For others to make good use of the forum, keep the discussion related to the subject title.
You started with gcc-4.1.2, but deviations from the topic do not aid others researching
problems. If you choose to use various compilers, use a more general title, or start
a different thread.
You mentioned patches that no longer work. The patches on the LFS book were for a
specific version, and not necessarily helpful for later compiler versions, as they need to
be checked against the ChangeLog and code to see if a similar patch was already made.
Readers would not know what patches you are using OR not using, so they may not
understand where you are at or going.
You started with gcc-4.1.2, but deviations from the topic do not aid others researching
problems.
All u would have to do is read the thread and u will see why I wanted to try and compile 4.2.2, because nothing I did to 4.1.1 was working. If 4.2.2 compiled then it would have to be something else other then my pc. That was my consensus. Do you feel that was wrong?
Besides, the original error I was getting when compiling 4.1.1 was due to my CPU apparently because once I switched out the single core for the dual core processor 4.1.1 compiled easily with no errors anywhere. I was most shocked, 3 days worth of errors, I wasn't expecting a new dual core processor to make that much of a difference.
Now I would like someone to explain to me how that happens. Because essentially that means the processor I bought is bad. But the sad part is I been using it for quite some time so there is no warranty anymore, but yet it is clearly an inferior product.
sry I was so confusing, but as u can see (hardware) CPU was never mentioned by anyone as a result of this error. I was lucky enough to have another processor sitting here to try. No offense, but I don't see anyone with any good advice on this board.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
