Change 3057
Fix mysterious rebuild problem: in an attempt to make 'jam -dc'
output report headers updates more accurately, internal (header
collection) targets were being bound as T_BIND_PARENTS so that
they could carry the timestamp of the actual source file. But
that caused the fate of the internal node to be marked as
T_FATE_NEEDTMP if anything they included was newer, and that
easily happens among header files (something is always newer
than something else). Now internal targets carry their parents
time, but with T_BIND_UNBOUND, like other NOTFILE targets.
Bug fix documented in RELNOTES.
=== computer:1666: Change 43415 by seiwald@play-seiwald on 2003/04/04 09:36:25
output report headers updates more accurately, internal (header
collection) targets were being bound as T_BIND_PARENTS so that
they could carry the timestamp of the actual source file. But
that caused the fate of the internal node to be marked as
T_FATE_NEEDTMP if anything they included was newer, and that
easily happens among header files (something is always newer
than something else). Now internal targets carry their parents
time, but with T_BIND_UNBOUND, like other NOTFILE targets.
Bug fix documented in RELNOTES.
=== computer:1666: Change 43415 by seiwald@play-seiwald on 2003/04/04 09:36:25