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.
So far so good until I got to 8.11.1. Installation of Readline
When ./configure is run I get
configure: creating ./config.status
./config.status: line 537: 0a1,162: command not found
./config.status: line 538: syntax error near unexpected token `newline'
./config.status: line 538: `> # This file is a shell script that caches the results of configure'
I had the same problem, here's what I have done to fix it. I think it is possible solution.
1. /dev wasn't mounted properly, I checked with findmnt on host and it wasn't there
2. I found it out, because in zstd make check returned "unexpectedly /dev/null is a regular file"
3. exited chroot
4. mounted /dev via 'mount -v --bind /dev $LFS/dev'
5. chrooted back
6. rebuild zstd and checked it
7. now I can make config for readline
Good point! A number of LFS chroot builds require a functional /dev system to work.
If you want to build LFS in stages at odd moments, you should create a script which you can run as root to carry out the various binds and mounts described in Chapter 7.3, followed by the chroot command in 7.4. Don't forget to define the LFS variable within your script!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.