Hi. > > > > > Well, the untarred files have timestamps of months ago, when the > developers > > made the package. Even untarring with -m and getting the current time > makes > > no difference. But I can post the part where it repeats: > > The untarred timestamps are irrelevant. It is the make target timestamp. > > The exact problem happened before at the exact same place. Setting the > system clock correctly apparently was the fix: > http://linuxfromscratch.org/pipermail/lfs-support/2010-May/038711.html > http://linuxfromscratch.org/pipermail/lfs-support/2010-May/038653.html > > Just a thought: The time from date and hwclock can be different. > > hwclock > Display Hardware Clock. > > hwclock --hctosys > Set the System Time from the Hardware Clock. > > hwclock --systohc > Set the Hardware Clock to the current System Time. > -
I read the messages but I couldn't make it work. I tried many things, playing with the hwclock settings, UTC/non UTC clock in the host system, putting TC=UTC before configure, and using several different settings in configure. I tried this because the configure in the first pass works always, and any other combination goes to the loop, always too. This was 64bits. I tried i686 with a 32 bit host, and everything has gone perfectly well. So, maybe it's clock related, but also architecture related. I'll try building for 64 bits again. We'll see... Alberto -- duende a rayas
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
