Werner LEMBERG <w...@gnu.org> writes:
>> It is almost certainly a problem with your system clock. If you have
>> touched source files with a future clock, and now the clock is right,
>> then compiled files will be outdated ("older" than the source file)
>> immediately after compilation again.
>
> There is a special built-in target in GNU make:
>
> `.LOW_RESOLUTION_TIME'
>
> Since `cp -p' discards the subsecond part of `src''s time stamp,
> `dst' is typically slightly older than `src' even when it is up
> to date. The `.LOW_RESOLUTION_TIME' line causes `make' to
> consider `dst' to be up to date if its time stamp is at the start
> of the same second that `src''s time stamp is in.
>
> Maybe this helps?
The system date of Janek pointed to next Friday. While this may yield
to `.LOW_RESOLUTION_TIME' when scaling the entire creation (according to
its appearance) into seven days, for normal purposes no special options
should be required to figure out that there is a disturbance in the
fabric of time as witnessed by Make.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
