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.
There obviously is a lot more output, but I think this is the relevant bulk of it. Unfortunately, I can't see what the actual error is. All I can determine is that check wasn't remade due to some errors.
All the output make check generated should be in the glibc-check-log logfile. All the errors are also in that file, did you take a look at it?
What output did the grep Error glibc-check-log show?
Also: Take a good look at the errors mentioned in the book, some errors are to be expected.
And maybe this will help: Index of /lfs/build-logs/development. The (test) log directories hold the output of the compile/make check steps done for the packages.
First: This is a development version, which could mean that some parts are still under construction.
Not sure if you can ignore this error (a quick search with "lfs glibc tst-cpuclock2" gives a ton of hits, but no real answer, but I did look quickly....).
You can have a look in the glibc-check-log log and see why tst-cpuclock2 failed. If there is no mention of missing commands/programs/files you could decide to continue. This package is known to throw some errors and those can be 'ignored' most of the time (as mentioned in the book).
The nptl/tst-clock2 and tst-attr3 tests sometimes fail. The reason is not completely understood, but indications are that a heavy system load can trigger these failures.
Admittedly, this LFS system is a time-killer and by no means a productive one. I won't really be out anything if it falls apart (maybe a waste of HDD lifespan).
that is a known failure and its expected. From what can be gleamed its because of the hoast system and the chroot environment or something or other I don't remember the particulars but its nothing to be concerned about.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.