[Scons-users] Bug MD5-timestamp and --debug=explain
bill at baddogconsulting.com
Wed Jun 3 18:30:34 EDT 2020
Please file a github issue with your example.
Ditto what Mats said..
On Wed, Jun 3, 2020 at 10:59 AM Mats Wichmann <mats at wichmann.us> wrote:
> On 6/3/20 3:46 AM, orenaud at coventor.com wrote:
> > Hi,
> > I observe a strange behavior of --debug=explain, when the MD5-timestamp
> > decider is used. When I change a single file, --debug=explain marks all
> > the "sibling" dependencies as "changed". It does not affect the build
> > itself though, as expected only the necessary files are recompiled.
> this isn't much of an answer, just sort of an ack to your ping...
> I see the same on a Linux system with your test. There's a testcase that
> should trigger this:
> but it doesn't, because it doesn't use an external command whose
> signature would thus be included in the implicit dependencies, it uses
> There have been a few issues with explain() not explaining very well.
> Fortunately (and as you've apparently surmised, as you've noted it
> doesn't impact the build), the explain function is completely separate,
> if you've asked for debugging at this level, and the decider decides a
> rebuild is needed, only then is it called, and it does its own
> calculations in preparing the messages eventually output.
> Scons-users mailing list
> Scons-users at scons.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Scons-users