Serge,

> I think scons might be ignoring the ambient environment (PATH,
> LD_LIBRARY_PATH, etc...) when it is run, instead setting up its own
> (presumably in the name of providing repeatable builds).

	scons does not by default pass variables from the environment in
which it is invoked to the processes it invokes, precisely to provide
repeatable builds.

| scons does not automatically propagate the external environment used to
| execute scons to the commands used to build target files. This is so
| that builds will be guaranteed repeatable regardless of the environment
| variables set at the time scons is invoked. This also means that if the
| compiler or other commands that you want to use to build your target
| files are not in standard system locations, scons will not find them
| unless you explicitly set the PATH to include those locations. Whenever
| you create an scons construction environment, you can propagate the
| value of PATH from your external environment as follows:
| 
|     import os
|     env = Environment(ENV = {'PATH' : os.environ['PATH']})

-- 
Kian-Tat Lim, LSST Data Management, [log in to unmask]

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1