GCC Pass1 - undefined reference to `GNU_USER_TARGET_OS_CPP_BUILTINS'
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.
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 3,137
Rep:
You first need to eliminate possible causes of errors TRY building in a folder IF you get the same errors then you know that the problem is not with the stick, if it builds OK then the problem is either with the stick itself or how it's being mounted.
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 3,137
Rep:
Quote:
Originally Posted by spiky0011
Hi
FTI I have built from HD host to usb HD all worked
I can't see why using a usb stick in general would cause a problem as you say you have done it, the problem may be that specific stick or the way its mounted etc, but it is an easy thing to check and that then eliminates that possible source of error, so far the op seems to be doing everything 'by the book', there is obviously something wrong somewhere, so first its best to eliminate the obvious and easy sources of possible errors.
I tried it all over again with a compact flash card and got the same error, so I looks like the usb stick wasn't the issue. It's still possible that the sources might have gotten messed up, even though the check-sums all matched when I first downloaded them, so I'm going to re-download them again (I copied the sources from the usb over to the compact flash). Testing on the hd is possible but only as a last resort since it will prove nothing other then it works on a hd... I still have to figure out why this doesn't work on a removable device since that is what I have to provide.
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 3,137
Rep:
Quote:
Originally Posted by richard620
I tried it all over again with a compact flash card and got the same error
You still haven't eliminated the possibility that the problem lies with the card just build the tool chain to a folder on your hard drive if that doesn't work then you KNOW th problem is not the card.
It does the same thing when I do it locally too. I keep getting a '/usr/lib64/libgmp.la can not be found' error the first time I run make for gcc, but it doesn't show up the second time I run make. It does the same thing when I was testing the remote drive. Other then that, I'm at a loose as to what's going on.
Distribution: Linux From Scratch, Slackware64, Partedmagic
Posts: 3,137
Rep:
the .la files are used by libtool and are basically a PITA and can usually be removed ( I removed all of them from my system ). what other errors are you getting?
Besides my original posted error, none. I'll hit make again after I get the first 'missing la' error and then I get the 'GNU_USER_TARGET_OS_CPP_BUILTINS' error.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.