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.
Over the next couple of days I plan to start making a new CLFS system. I ran into some issues the last time I began, partially because the host I was using wouldn't allow me to go the chroot method instead of the boot method. Can anyone suggest a good host system to use for an x86_64 build? Currently I'm using Ubuntu 10.04 LTS. If it's just a matter of having the correct packages, what dev packages are key to allowing me to chroot rather than have to boot? If it's actually an architecture concern, please suggest a better distro that will work.
chroot isn't part of any of the dev packages. It's part of coreutils and should be automatically included in any distro.
Figuring out why you were unable to chroot will depend on the error message you got. A couple things to keep in mind: you should enter the chroot command from the clfs book as root. If you su, and it says it cannot find the chroot command, it's possible you didn't get root's path when you executed su. you may have to enter the command with the full path to chroot: "/usr/sbin/chroot"
I've built clfs in Ubuntu 9.10, and I am currently building it on a new system with Fedora 14 as the Host.
Many prefer using a live cd or slackware as their hosts. It's possible to do in any of these, just make sure you have gcc, make, flex, bison, etc installed.
I appreciate the reply, but I guess I was unclear as to exactly what my issue was. Following Chapter 6 of the CLFS book, you have the option to boot or chroot to finish the job. The book states,
Quote:
If you are in any doubt about this, you can try the following commands to see if you can chroot:
During my last build attempt, these tests failed, leading me down the boot method. Along the way I ran into a few other issues and ended up setting the project aside, and have just returned to it. Now, it's been several months, and I don't remember exactly how they failed, but I assumed that failure indicated an issue with the host system allowing me to complete the installation using the chroot method over the boot method. I hope that is a little more clear. I've no issue using the chroot command, but rather during my last adventure I ran the above commands and it told me to boot, and I'd much rather chroot through Chapter 7. Since I'm not 100% certain what the above commands are telling me, a little clarification in their purpose would probably go a long way toward solving me dilemma as well, if anyone is able to explain it.
at the section about To Boot or to Chroot, this is what I get.
Code:
clfs@thebeast:/mnt/clfs/sources$ /tools/lib/libc.so.6
GNU C Library (EGLIBC) stable release version 2.12.2, by Roland McGrath et al.
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.5.2.
Compiled on a Linux 2.6.37 system on 2011-02-08.
Available extensions:
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
Native POSIX Threads Library by Ulrich Drepper et al
BIND-8.2.3-T5B
libc ABIs: UNIQUE IFUNC
For bug reporting instructions, please see:
<http://www.eglibc.org/issues/>.
clfs@thebeast:/mnt/clfs/sources$ /tools/lib64/libc.so.6
bash: /tools/lib64/libc.so.6: cannot execute binary file
clfs@thebeast:/mnt/clfs/sources$ /tools/bin/gcc -v
bash: /tools/bin/gcc: cannot execute binary file
Any assistance would be appreciated. I'm going to attempt a Package Users build and it would be so much easier to chroot and have access to quick research if I run into any trouble.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.