Re: [Scons-dev] Using SCons via bootstrap.py

2013-05-17 Thread Russel Winder
I updated to 2870:1bdda9a31f35 which is just prior to the new documentation tool set change of 2013-05-03 and everything works as it should. Looking up the changes I see that 2888:102c1bf4e8cd makes changes to bootstrap.py and I can confirm that this changeset breaks things for me: 2887:2126e0af53

Re: [Scons-dev] Using SCons via bootstrap.py

2013-05-17 Thread Russel Winder
On Sat, 2013-05-18 at 00:57 +0200, Dirk Bächle wrote: > Hi Russel, […] > the bootstrap.py works fine for me, I guess because I have a > "src/engine" folder. Where did yours go? ;) Still exactly where it has always been, in the repository: |> python /home/users/russel/Repositories/Mercurial/Mast

Re: [Scons-dev] Using SCons via bootstrap.py

2013-05-17 Thread Dirk Bächle
Hi Russel, On 17.05.2013 19:13, Russel Winder wrote: Is anyone else finding that the bootstrap.py script no longer works? It worked for me before I went away for a short break and now after updating Debian Unstable, it is failing. I get the same behaviour with Python 2.6, 2.7 and PyPy 2.0. Trac

Re: [Scons-dev] Using SCons via bootstrap.py

2013-05-17 Thread Russel Winder
On Fri, 2013-05-17 at 14:43 -0400, Gary Oberbrunner wrote: > Are you at the tip of the default branch? Of course. How else can you be at the bleeding edge ;-) -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voi

Re: [Scons-dev] Using SCons via bootstrap.py

2013-05-17 Thread Gary Oberbrunner
Are you at the tip of the default branch? On Fri, May 17, 2013 at 1:13 PM, Russel Winder wrote: > Is anyone else finding that the bootstrap.py script no longer works? It > worked for me before I went away for a short break and now after > updating Debian Unstable, it is failing. I get the same

[Scons-dev] Using SCons via bootstrap.py

2013-05-17 Thread Russel Winder
Is anyone else finding that the bootstrap.py script no longer works? It worked for me before I went away for a short break and now after updating Debian Unstable, it is failing. I get the same behaviour with Python 2.6, 2.7 and PyPy 2.0. Traceback (most recent call last): File "/home/users/russ

Re: [Scons-dev] Corrupt cache?

2013-05-17 Thread Tom Tanner (BLOOMBERG/ LONDON)
It appears that something is not causing the md5 of the contents to be recalculated. I can do this pretty consistently. I added some trace that prints out the stored md5sum of the object and I get this sort of things: scons: Building targets ... x.test.o 42f3caacf79d52342143ae0708d5c773 libthing

Re: [Scons-dev] Corrupt cache?

2013-05-17 Thread Gary Oberbrunner
[Tom, this is probably more of a scons-us...@scons.org question; moving to that list. -- Gary] SCons can warn if it can't copy something to the cache, if you turn on --warn=cache-write-error (it's off by default). Unless you're doing something unusual with deciders or custom signatures, I don't s

[Scons-dev] Corrupt cache?

2013-05-17 Thread Tom Tanner (BLOOMBERG/ LONDON)
I've recently had a problem with some object being copied to the cache *but* the copy didn't happen because the target thing already existed, but the new object and old object had different md5sums. Not surprisingly this causes very strange problems when the files get copied from the cache. I'm