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.
Are we talking about chapter 5 (toolkit) or chapter 6 (final versions)? I notice that you have a multilib setup, so it is unlikely to be chapter 6 which must be done in chroot. LFS itself does not do multilib, though Debian does. Your ldconfig printout isn't relevant as it is clearly the one from the Debian host.
Are you sure your new bzip2 was installed in $LFS/tools and that you are running it as the lfs user with the correct environment? What is the output of "echo $PATH"?
Your path is correct but the ldconfig output still looks weird. It seems to be picking up directories from the host's /etc/ld.so.conf file. Those 32-bit directories, libx32 and /usr/libx32 are not present in LFS so they should not be searched for in the chroot environment. What does the LFS /etc/ld.so.conf file look like?
Don't just start again from chapter 5. It's very likely that something went wrong in chapter 4, when you were setting up the environment. When you get really weird results, that's often where the problem lies. It will save time in the long run if you go through that chapter again carefully and make sure you have done everything exactly as specified before you start building your toolset.
Don't beat yourself up! The first LFS build never works.
Thanks for the motivation. This was my fifth try. I always mess up something or the other at some point. Let's see if I can pull this off this time.
Thanks again for the piece of advice.
I realised that all this while I was using kernel version 3.16, while the recommended kernel version is 3.2+
Probably that was the cause of the error.
Started afresh on a Fedora VM running Linux kernel version 4.2
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.