I just did some searching and found this. http://comments.gmane.org/gmane.comp.programming.tools.scons.user/20816
Have you tried scons 1.3? Maybe it's fixed. Ali Sent from my ARM powered device On Mar 23, 2011, at 11:39 PM, Steve Reinhardt <[email protected]> wrote: > I think many of us have noticed that scons sometimes rebuilds things > when it's not necessary. Here's one clue: > > % scons build/ALPHA_SE/m5.debug > scons: Reading SConscript files ... > [...] > scons: done building targets. > % scons --debug=explain build/ALPHA_SE/m5.debug > scons: Reading SConscript files ... > [...] > [ SWIG] ALPHA_SE/python/swig/core.i -> _wrap.cc, .py > scons: rebuilding > `build/ALPHA_SE/python/m5/internal/vptype_AddrRange.py' because the > dependency order changed: > old: > ['build/ALPHA_SE/python/m5/internal/vptype_AddrRange.i', > '/usr/bin/swig', 'build/ALPHA_SE/base/range.hh', > 'build/ALPHA_SE/base/types.hh', 'build/ALPHA_SE/python/swig/range.i'] > new: > ['build/ALPHA_SE/python/m5/internal/vptype_AddrRange.i', > 'build/ALPHA_SE/base/range.hh', 'build/ALPHA_SE/base/types.hh', > 'build/ALPHA_SE/python/swig/range.i', '/usr/bin/swig'] > [...] > > > This is just one of many swig files that get regenerated... most of > the dependency lists are much longer, but in all of the ones I looked > at, /usr/bin/swig had moved from the second spot to the last spot on > the list. > > Subsequent rebuilds say that " `build/ALPHA_SE/m5.debug' is up to > date", but if I delete build/ALPHA_SE/python/m5/internal then it takes > *two* builds to get it back to that state again. > > Any ideas, Nate? > > Steve > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
