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.
different distro different result. I installed LRs LFS and changed nothing in the way I was doing things and I am currently about 1/2 way through the LFS book. Dont understand why it works on LRs and not slack. Any insight would be appreciated as I would like to understand this. Thanks
did you follow the instructions in the book about creation of user 'lfs'..? have you given proper permission to the downloaded package directories to 'lfs'.. you can give permission by entering "chown -R lfs /directory/of/packages" in the terminal..
UH, do you have "devpts" enabled in the $host kernel??
unless your host system has it working, LFS will give this error.........
it will be the same with /proc
the "virtual processes" have to be working on the $host system for LFS to
enable it.........you will need devpts and /proc working in order to enter the chroot environment in chapter 6!!
I had the same problem so I unpacked all the sources my way in installed them my way and just used there prefixs and other junk ...lol works for me... I think the documentation is poorly done though... but thats just my opinion.
I unpaked all the sources read there readme's and did what I was told.
simple as that all I use the guid fore is to compile what packages in what order I didn't really care what it said about anything else...
Originally posted by CryptDragoon I had the same problem so I unpacked all the sources my way in installed them my way and just used there prefixs and other junk ...lol works for me... I think the documentation is poorly done though... but thats just my opinion.
I thought the documentation was great. It walked you through every step(held your hand), and told you exactly what everything did. I was completely satisfied by the books documentation
If you batch retrieved packages you might have to unpack the tarball as follows:
tar -jxvf binutils-2.14.tar.bz2
mkdir binutils-build
cd binutils-build
============================
why is this a bug?
if you read the introduction in chapter 5 which says:
Quote:
It is also expected that you have already unpacked a source package (while logged in as user lfs -- explained shortly) and performed a cd into the source directory of a package before issuing its build commands
then the instructions make sense (at least to me).
if you still think it is a bug, you also have to report pretty much all build instructions in the book, because they all assume that you start in the source directory of the package you are going to build.
Originally posted by shanenin I thought the documentation was great. It walked you through every step(held your hand), and told you exactly what everything did. I was completely satisfied by the books documentation
D00d what they give you n example of what you have to do it should NOT be done like this... people who give examples should be shot!
#mkdir ../binutils
That can be anywhere!
It should have been like this:
/# cd sources
sources#mkdir ../binutils
See THAT is how to make porper documentation! not the LFS way!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.