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.
@Rodano: You can change anything you want, it is your LFS build. But.....
Nothing needs to be added, removed or changed. If you run into a problem then you made a mistake and "solving" the problem by doing things that aren't mentioned in the book will get you into trouble later on. The book works as-is and this is proven by many others that build LFS 7.4 successfully.
The above statement is a bit black and white, but I'm assuming that this is your first LFS build and you are having problems in the very early stage of the build which normally points to an invalid host or a misunderstanding of (one of) the concepts/steps that are in the book.
The only way to find out what is wrong is by eliminating stuff, one at the time. As suggested earlier, I would start with a host that hasn't been tampered with (the host glibc issue and its possible consequences).
You can add stuff to LFS, but you are kinda on your own if you deviate from the boot. BLFS is where you should worry about customizations, not LFS. LFS is just an OS core, a basic and simple raw OS with just tools, and you shouldn't deviate the core outside the known working parameters.
To be honest, the tips post I wrote about specifically warned against this, because it makes diagnosis of the build issues extremely problematic.
The book is VERY specific in what it calls for. If anything, the ONLY deviation you probably could get away with and not get any issues with, might be the Kernel, such as using 3.11.1 in place of 3.10.10.
@Rodano: You can change anything you want, it is your LFS build. But.....
Nothing needs to be added, removed or changed. If you run into a problem then you made a mistake and "solving" the problem by doing things that aren't mentioned in the book will get you into trouble later on. The book works as-is and this is proven by many others that build LFS 7.4 successfully.
The above statement is a bit black and white, but I'm assuming that this is your first LFS build and you are having problems in the very early stage of the build which normally points to an invalid host or a misunderstanding of (one of) the concepts/steps that are in the book.
The only way to find out what is wrong is by eliminating stuff, one at the time. As suggested earlier, I would start with a host that hasn't been tampered with (the host glibc issue and its possible consequences).
I tried to install lfs on my netbook with clean wheezy but i've the same problem. Also i have a question - is this command nesessary?
sed -i -e 's/static __m128i/inline &/' sysdeps/x86_64/multiarch/strstr.c
I tried to install lfs on my netbook with clean wheezy but i've the same problem.
Assuming that your netbooks host is compliant: You must be doing something wrong at some stage (not necessarily the glibc chapter). Without knowing which steps you did (and how/where they were done) it is hard to point you to something specific.
The learning experience aside; Once your host is compliant, LFS is basically a copy/paste exercise.
Quote:
Also i have a question - is this command nesessary?
sed -i -e 's/static __m128i/inline &/' sysdeps/x86_64/multiarch/strstr.c
I answered that already in my previous reply:
Quote:
Nothing needs to be added, removed or changed.
Stop trying to "fix" the book, there's nothing wrong that needs fixing
My advise: Remove everything LFS related and start from scratch and do start with the first chapter in the book.
Assuming that your netbooks host is compliant: You must be doing something wrong at some stage (not necessarily the glibc chapter). Without knowing which steps you did (and how/where they were done) it is hard to point you to something specific.
The learning experience aside; Once your host is compliant, LFS is basically a copy/paste exercise.
I answered that already in my previous reply:
Stop trying to "fix" the book, there's nothing wrong that needs fixing
My advise: Remove everything LFS related and start from scratch and do start with the first chapter in the book.
I tried to install it from 1 stage on two notebooks and the result scratch the brain. As is written in the book:
"The LFS system will be built by using an already installed Linux distribution (such as Debian, Mandriva, Red Hat, or SUSE)."
Maybe i should use another distribution?
I've successfully installed various LFS versions on:
- Debian
- Slackware
- Ubuntu
- Suse (old experience, talking about the 2003/2004 era)
Most hosts need to be made compliant (modern Slackware version is the exception if I recall correctly), but once they are compliant it doesn't really matter which host is used.
Debian is my personal choice (if no other LFS host is available) and I've successfully build 7.0, 7.1 and 7.2 on Squeeze and 7.4 on Wheezy.
I've successfully installed various LFS versions on:
- Debian
- Slackware
- Ubuntu
- Suse (old experience, talking about the 2003/2004 era)
Most hosts need to be made compliant (modern Slackware version is the exception if I recall correctly), but once they are compliant it doesn't really matter which host is used.
Debian is my personal choice (if no other LFS host is available) and I've successfully build 7.0, 7.1 and 7.2 on Squeeze and 7.4 on Wheezy.
Can it depends on hardware or different gnu's? On 1st machine i've installed cinnamon, on 2nd - xfce.
LFS is based on AMD/Intel x86 (32-bit) and x86_64 (64-bit) CPU architecture. If I look at the output posted by you then I see i686, which would point to a 32 bit x86 cpu. No problem there.
Quote:
or different gnu's? On 1st machine i've installed cinnamon, on 2nd - xfce.
Nope.
I've installed using CLI, Gnome, KDE and Xfce. I do prefer the CLI, but that is a personal choice.
Not to poke a dead horse, but honestly, it gets rather annoying and tediously bothersome attempting to diagnose an issue when someone deviates from the instructions of the authors LFS and neglects to say so.
The point of the book is to help you build a "Core GNU/Linux OS" that you can later customize using BLFS, or your own stuff. The authors poured over bugs in the development stage SVN books to make sure anything published publicly denotes a successful compile on their part for the release stage book.
When you deviate, honestly, we can not help you, because we don't know what you did.
Sorry to be blunt and direct, but honestly, I feel like saying at times, "Start over, read, and follow the damn book this time!"
Not to poke a dead horse, but honestly, it gets rather annoying and tediously bothersome attempting to diagnose an issue when someone deviates from the instructions of the authors LFS and neglects to say so.
The point of the book is to help you build a "Core GNU/Linux OS" that you can later customize using BLFS, or your own stuff. The authors poured over bugs in the development stage SVN books to make sure anything published publicly denotes a successful compile on their part for the release stage book.
When you deviate, honestly, we can not help you, because we don't know what you did.
Sorry to be blunt and direct, but honestly, I feel like saying at times, "Start over, read, and follow the damn book this time!"
I haven't deviated the book instructions when built lfs. I just asked a question about the possibility, so u are not right here.
Then I have to ask... do you have the proper *-dev packages for the requires packages installed on your system and are you using BASH as the primary shell?
Then I have to ask... do you have the proper *-dev packages for the requires packages installed on your system and are you using BASH as the primary shell?
I find binutils without "-dev". Maybe there are another programs without dev. i'll seach them...
I find a strange thing: when a lfs user and group are added to system and i try to log in it in an other tty it writes there is not such user in a system.
Does your system have Sudo installed and enabled by default with the root user account blocked from login?
Sudo is installed. hm.. When i try to use "sudo + cmd" in not root account there is an error: #name is not in sudoers file. This incident will be reported.
Also i find there is a package "linux-image-3.2.0-4-686-pae installed but linux-headers packege isn't installed on my system. Should i install it?
Also should i install "debug" packages or it is unnecessary?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.