I'm following the 4.1 book closely. Have reached Chap. 6, installing Glibc-2.3.1.
Make ends up with this:
//--------------------------
/usr/src/glibc-build/string/strcat.o: No space left on device
/tmp/cc9JyU5c.s: Assembler messages:
/tmp/cc9JyU5c.s:284: FATAL: Can't write /usr/src/glibc-build/string/strcat.o: Illegal seek
make[2]: *** [/usr/src/glibc-build/string/strcat.o] Error 1
make[2]: Leaving directory `/usr/src/glibc-2.3.1/string'
make[1]: *** [string/subdir_lib] Error 2
make[1]: Leaving directory `/usr/src/glibc-2.3.1'
make: *** [all] Error 2
I have no name!:/usr/src/glibc-build#
//--------------
That implies no disk space. I have 4.3 GB free for the lfs partition.

However, issuing df from the chroot enviornment gets me this:
//--------------
I have no name!:/usr/src/glibc-build# df
Filesystem 1k-blocks Used Available Use% Mounted on
I have no name!:/usr/src/glibc-build#
//--------------
no numbers just the headers for df.

I have searched google and elsewhere to no avail.
Anyone give me some clues?
Thanks,
Curt

You need to provide df with a partition or a directory, like:
df /dev/hda
df .

The reason you don't get anything with just plain df is because df consults your fstab file to list all the filesystems. Well, you haven't created one yet, so it thinks there are no filesystems, and quits.

EDIT:
Don't put money on the comment about reading fstab... the man pages don't seem to say that explicitly. However, I'd have to imagine that since you chroot'ed into your current environment, and have not mounted the / filesystem (or any others) manually, then there's no way for df to know what filesystems ARE mounted. Make sense? I'm not sure if it does either..

EDIT #2:
I'm also no expert, but 4 gigs should be enough, unless you keep absolutely everything (like all source trees after install, all packages uncompressed, etc). You might be running out of inodes instead of plain old disk space.

Thanks for the input. Makes sense.

I have no name!:/usr/src/glibc-build# df /dev/hdb10
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hdb10 5932297 1138510 4486546 21%

This verifies diskspace is not the problem.

Are you keeping all the old source trees? If you're willing to get rid of one, try that and recompile. If not, then go through all the trees you have and try "make clean" to get rid of the no longer needed files (it will still leave the source code intact). If you get further, then it's because you're running out of inodes, and you'll have to tidy up things to continue.

Dark_Helmet !
You are a genius and a schollar
Guess now, I owe you a dollar.

Yes I had kept the old source trees. Why not plenty of disk space?
I deleted about 8 of the larger ones, and make just finished sucessfully.

I do recall now, THE BOOK did say to delete the source trees.
Guess I wasn't following a closely as I thought.

I know nothing about inodes. My eyes have always glazed over, and I turn the page, when inodes has been discussed. I will now learn.
After all, that is why I'm installing LFS !

Thanks for your time,
I appreciate your help,
Curt

Hehehehe... I'm sure I'll think of SOME way you can pay me back...

Well, the book suggests getting rid of the source trees only if you're low on space. I don't keep them around. I configure, compile, install, and remove them. I keep the packages and patches in compressed form in case I need to look at it later, but that's not a rule or anything.

As for the inodes... I glazed over myself. I know you need 1 inode per file. Beyond that, I don't remember the benefits/penalties are for increasing the number of inodes... I know if impacts your storage capacity somehow.

ANYWAY, I'm glad it worked, and I'll start thinking of something fiendish for payback...