Hi Jason,
On 05.04.2014 00:17, Kenny, Jason L wrote:
I think yes, in that it does what should be done by the system under
posix_spawn.. ie call vfork and execve.
Here is the last version of the monkey patch I have from the people
working on it. It has a fallback to the classic fork exec if the API's
don't exists. It seems to solve the main speed problem for us at the
moment. I believe it still being tested to find possible issues.
I tried to let SCons run with this patch, but I'm not able to integrate
the patching of subprocess.Popen() successfully. I always get an import
error for SCons.Util, and fail to see where this is actually coming from:
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
gcc -o d1_0/f00000_sconsbld_d1_0.o -c -Id1_0/lup000_sconsbld_d1_0
-Id1_0/lup001_sconsbld_d1_0 d1_0/f00000_sconsbld_d1_0.c
Traceback (most recent call last):
File
"/home/dirk/workspace/scons_dirkbaechle/src/engine/SCons/Platform/posix.py",
line 42, in <module>
import SCons.Util
ImportError: No module named SCons.Util
scons: *** [d1_0/f00000_sconsbld_d1_0.o] Error 1
scons: building terminated because of errors.
Does anybody have a clue and can give me a pointer? I'd like to compare
the times for a clean build against the default sources.
Regards,
Dirk
_______________________________________________
Scons-dev mailing list
Scons-dev@scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev
