I have this problem:

Looks like a nasty problem to be solved before I can leave e2fsprogs.

Hi,

I see 2 problems:

First: Did you skip a step? The file should be there (I just checked on my box).

Check to see if /usr/share/info/libext2fs.info is present. If it is then it is already unzipped and that specific step is ok (don't ask me how that could have happened).

If these errors are the only errors you encountered, you could decide to continue. The failing commands create/adjust the info and doc pages related to e2fs. On the other hand: Info and doc pages are kinda handy to have......

Second: The missing command (install-info) is part of texinfo, which you installed (??) in chapter 5 (5.30.1 to be precise)

Install-info should be installed. Check to make sure it is (/mnt/lfs/usr/bin should hold both install and install-info).

Hope this helps.

Thanks for the pointer druuna!

shucks! From the log file, I found that I didn't do the texinfo build.
(I must have too tired or what?)

I don't have /usr/share/info/libext2fs.info.gz
using cd and ls. I guess since texinfo is not installed properly, the file libext2fs.info.gz is not copied over during the e2fsprogs build.
I will check if this file is in the e2fsprogs tarball.

texinfo was the last package in chapter 5 and I messed up.. sigh..

Hi,

Although it is not nice to mess up, it is a good thing you have all the log files. At least now you definitely know what went wrong, nothing worse then not knowing and having to guess where the ball was dropped.

Did you make a backup of everything up to the end of chapter 5 (mentioned in 5.32, the Caution part)? If you did you can erase everything, unpack the backup, add texinfo, create a new backup and start fresh with chapter 6.

my tar may have some content resulting from

When I started Chapter 6 I forgot to backup as mentioned in the last section of chapter 5. But then suddenly realized that I need to
do a backup after the commands above.
Do you think the backup file for Chapter 5 is still okay to use ?

I am particularly worried about the mknod.

Any sure way to "undo" my mknod action, such as rm $LFS/dev/console and null ?

anyway, I may just simply go ahead to untar the slightly corrupted tar file, build texinfo, do a backup and start the long journey with chapt 6.

it seems like I have worried too much. I basically have to make sure that
/mnt/lfs is only filled with (by moving the old files to somewhere else) tools and sources at the beginning.
So mknod does not affect anything.

0 members found this post helpful.