LFS installation breaks in Binutils final compilation (Section 6.13)
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.
I don't know which version of LFS you are trying to build, but it seems to me you're trying to include gold linker. That was just recently added, and the order of the packages was properly adjusted, and even bison was added into chapter 5. If the problem persists, try using --disable-gold, or remove any *-gold flag if you have any, but have not yet adjusted to new package order, or have bison installed in chapter 5.
I don't know which version of LFS you are trying to build, but it seems to me you're trying to include gold linker. That was just recently added, and the order of the packages was properly adjusted, and even bison was added into chapter 5. If the problem persists, try using --disable-gold, or remove any *-gold flag if you have any, but have not yet adjusted to new package order, or have bison installed in chapter 5.
I too am following the LFS 8.0 current stable (not systemd) book and have bumped into an issue checking the build of "bunutils 2.27".
The base system is Slackware 14.1 (i386), the build of the "tools" went OK (I think), and CHROOT into the final emvironment. Build and check of items to "binutils 2.27" appears to have been successful. The binutils build also went fine as no errors jumped at me.
However, the "gold" issue crops up during the check phase of binutils with the following:
==================
All 3 tests passed
==================
make[5]: Leaving directory '/usr/src/source/binutils-2.27/build/gold'
make[4]: Leaving directory '/usr/src/source/binutils-2.27/build/gold'
make[3]: Leaving directory '/usr/src/source/binutils-2.27/build/gold'
make[2]: *** [Makefile:940: check-recursive] Error 1
make[2]: Target 'check' not remade because of errors.
make[2]: Leaving directory '/usr/src/source/binutils-2.27/build/gold'
make[1]: *** [Makefile:6133: check-gold] Error 2
make[2]: Entering directory '/usr/src/source/binutils-2.27/build/gprof'
make check-recursive
make[3]: Entering directory '/usr/src/source/binutils-2.27/build/gprof'
Making check in po
make[4]: Entering directory '/usr/src/source/binutils-2.27/build/gprof/po'
make[4]: Nothing to be done for 'check'.
snipped until the end ....
make[3]: Leaving directory '/usr/src/source/binutils-2.27/build/libiberty/testsuite'
make[2]: Leaving directory '/usr/src/source/binutils-2.27/build/libiberty'
make[1]: Target 'check-host' not remade because of errors.
make[1]: Nothing to be done for 'check-target'.
make[1]: Leaving directory '/usr/src/source/binutils-2.27/build'
make: *** [Makefile:2205: do-check] Error 2
make: Target 'check' not remade because of errors.
I will go away and build binutils using "disable-gold" as noted above and let you know how the check turns out.
I just put together my LFS build within the last week, and, in my experience, the tests throw a ton of errors. Generally, if they are at the end when its leaving the build directory, like this...
... its no problem. Just expect it to fail out at the end of testing. Why? I have no idea, but a majority of them do, and it didn't have any measurable effect on my build. Mine works just fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.