Hi. This is not the first time which happens to me. When i try to compile something and the clock is not set or is wrong, make will permenently try to use a Makefile.in saying which has modification time in the future. The first time, i update the system clock and it works. Now i do a emerge --update --deep --newuse world and the same error ocurrs with binutils i fix it adding ten minutes to the real time and it works at the moment but i cant understand why, if the system clock is ok it should work fine. I dont know if it is really a bug, but you will know what to do.
No, broken system clock is not a Gentoo bug. :=) Also, you should wipe ${PORTAGE_TMPDIR} after fixing your clock issues before you try to compile again.
The system clock is just fine, setted to the local time, and gentoo update it fine, but before compile anything i have to "move up" the hour for 10 minutes (i dont know the word to tell in english). Example: mi real local time is : 19:15 27/12/2005 and i have to configure: 19:25 27/12/2005 to make it work with make, if not it says which the modification time is in the future. But i have to hack my clock to make it think i am on the future. thanks anyway.
