Hello,

I am in section 6.49 (E2fsprogs-1.43.1) of the LFS book v7.10. I am getting three failed tests for . The three failed tests are: m_minrootdir, m_rootdir and r_32to64bit.

Does anyone know how to fix these errors, or if they are normal. If additional information is required please ask. Thank you all!

m_minrootdir, m_rootdir might be failing because you're in chroot. I have seen that error several times and ignored it without issue.

I don't know about r_32to64bit, but I'm going to speculate that it has to do with a binary translation option not being selected in the kernel.

Edit: Specifically...

Executable file formats / Emulations --->
[ ] x32 ABI for 64-bit Mode

Try plopping an asterisk in there and running the check again.

Sorry, I am quite a beginner at the whole LFS system, where can I find the kernel to edit that? I know I built it for the tools/ dir earlier but have no idea where it was installed to.

You don't edit the kernel you edit the config file and then rebuild the kernel, see here:

http://www.linuxfromscratch.org/lfs/...08/kernel.html

What you built for /tools wasn't the kernel itself, only the kernel headers, because the glibc build needed them. You don't have a kernel yet. And the kernel you would need to rebuild is the one on your host system because that's the one you use in chroot. Frankly that would be using a sledgehammer to crack a nut.

You can find example logs of all the tests at http://www.linuxfromscratch.org/lfs/...00MQ/test-logs. That's always the first place to go if you are worried about errors. Generally speaking a single error (plus those that the book describes as expected) is nothing to worry about. Three, I agree, is a bit more serious. You can always post a question on the LFS mailing list if you are really worried.

Thanks for the response. It was only one proper failed test as the other two are failed as well in the logs, which you provided (Thank you!). Weirdly there are four tests which convert from 32 to 64 bit but the other three passed, so think I will remake the package and if the error persists, will just move on, because as you said it's using my host kernel, and as that wouldn't be on my LFS system there shouldn't be a problem.

After re-making the package all the usual tests passed, will do that next time! Thanks to everyone that helped.

Then you've learned another valuable lesson about building LFS: Test results are ephemeral. Many of the "torture" tests assume they're running on a dedicated test machine. When you're building in a virtual machine, or on a desktop and decide to play music, watch youtube, etc. while the tests are running it, can cause some to fail. In other words a failing test might not be an issue. A consistently failing test could be a problem, but not necessarily. A whole lot of tests failing on within the same test suite is a much better indication that something is wrong.

Yes I have, and glad I learned it on my first LFS system!