6.0-STABLE buildworld (possibly) broken ?

[Victor Snezhko]

Ruslan Ermilov <ru at freebsd.org> writes:

>> This problem seems to come up fairly regularly.  How about adding a
>> check into make(1) so that if a dependency has a date in the future,
>> make dies with more intuitive error?  It would probably reduce the
>> number of these questions if you got an error message like:
>> "foo.c was created in the future.  Check your system date/time."
>> 
>> IMHO, that's a lot more obvious than:
>> "/usr/obj/usr/src/tmp/usr/bin/ld: cannot find -lc"
>> or
>> "... touch not found ..."
>> 
> I considered doing this in make(1) a while ago, but have come
> to a conclusion it's not quite safe.  For example, I often
> "cvs update" from remote repositories, and that sets modification
> time to that of the repository machine (probably only if it's a
> new file, I don't recall all the conditions now, or it might
> have been NFS-mounted src/ or repo).

We could add a flag such as NO_TIME_CHECK or so and check only if
the flag isn't set.

-- 
WBR, Victor V. Snezhko
EMail: snezhko at indorsoft.ru