On Wed, Jan 2, 2013 at 10:24 PM, Ken Moffat <[email protected]> wrote:
> If you want to debug it, perhaps you could mount a partition from > the host system somewhere under your LFS, then untar a package in > both, compare the outputs of ls -lR, run configure in both, then > again compare the outputs from ls -lR. I suspect this (provided you > can mount the conventional disk - /mnt seems a likely existing > directory to try ) will show that the runs on the spinning rust are > now a lot more reliable. Problem solved! I decided to look through the bin directories for any discrepancies between the system on the USB and the backup I made (just in time!), which is on an SD card (I have a bad habit of using portable storage for things...) In the /usr/bin directory there was a big 0 listed for the size of the gawk binaries. You were spot on about the corruption, I'm guessing one bad block ruined the entire gawk binary. Interestingly, TWO files were completely wiped, though they were identical (gawk and gawk-4.0.1). They didn't seem to be linked but I don't know enough to fully explain it. Anyway copying the two files over from the backup appears to have fixed everything. Hopefully no more crucial binaries or libraries get wiped out... Thanks for the help! Alex
-- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
