[SOLVED] LFS 7.8-systemd 5.7 glibc error: Need linker with .init_array/.fini_array support
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: Void, Linux From Scratch, Slackware64
Posts: 3,150
Rep:
I agree with Krejzi run the commands manually first to verify that they are working then use a script, but saying that your scripts look OK, and the commands look right, but it may be something subtle in the scripts.
Just a thought have you linked /tools to /mnt/lfs?
Of course, scripts can make mistakes, but the commands (well, the dangerous ones) are being echoed to a log file and inspected.
The advantage is obviously that you can much more quickly rebuild but also that tou can still see what you've done several sessions ago, as has proved the case here: /tools pointed correctly (though thanks for the suggestion Keith) but binutils were compiled with --with-sysroots=$LFS instead of --with-sysroot=$LFS.
So the thread is solved.* Thanks everyone.
[So, for future readers with this error: the fault is probably in binutils and check the --with-sysroot option].
*Except for knowing how to mark the thread SOLVED. Hopefully that is easily answered.
Distribution: Void, Linux From Scratch, Slackware64
Posts: 3,150
Rep:
Quote:
Originally Posted by Michael Farthing
Of course, scripts can make mistakes, but the commands (well, the dangerous ones) are being echoed to a log file and inspected.
The advantage is obviously that you can much more quickly rebuild but also that tou can still see what you've done several sessions ago, as has proved the case here: /tools pointed correctly (though thanks for the suggestion Keith) but binutils were compiled with --with-sysroots=$LFS instead of --with-sysroot=$LFS.
So the thread is solved.* Thanks everyone.
[So, for future readers with this error: the fault is probably in binutils and check the --with-sysroot option].
*Except for knowing how to mark the thread SOLVED. Hopefully that is easily answered.
Those s's are sneaky!
To mark a thread 'SOLVED' click ont the 'Thread Tools' at the top and click 'Mark Thread Solved'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.