Opened 18 years ago
#43 new defect
Environment different if command executed locally of with a cmt broadcast
| Reported by: | Owned by: | arnault | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | a. Usage | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | OS: | All | |
| If Other, could you precise: | Experiment: | Atlas | |
| If Other, could you precise: | |||
| Stack trace: |
C:\LHCbSoft\GAUDI\GAUDI_HEAD\GaudiAlg\cmt>path
PATH=C:\LHCbSoft\contrib\CMT\v1r18p20060606\VisualC;C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE;C:\Pr ogram Files\Microsoft Visual Studio .NET 2003\VC7\BIN;C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools;C :\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\bin\prerelease;C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\bin;C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\bin;C:\WINDOWS\Microsoft.NET\Fra mework\v1.1.4322;C:\LHCbSoft\scripts;C:\LHCbSoft\lcg\external\Python\2.4.2\win32_vc71;C:\WINDOWS\system32;C:\WINDOWS;C:\ WINDOWS\System32\Wbem;C:\PROGRA~1\ULTRAE~1;C:\Program Files\cvsnt;C:\Program Files\PuTTY;C:\Program Files\TortoiseCVS;C: \cygwin\bin;C:\Program Files\Microsoft Visual Studio .NET 2003\DF98\BIN |
||
| Steps to reproduce: | |||
Description
I noticed that the environment variables are different when building a package if the command is executed locally in the <package>/cmt or if executed with a 'cmt broadcast' from a parent project. It seems that the child project 'inherits' all the environment of the parent without having set them in the shell. I do not think this is correct since you get different behaviour if the command is executed locally or from a cmt broadcast. In particular I am sufferering from the length of PATH. If executed locally the package builds normally. If executed from the parent package the PATH gets too long and the build fails.
Note: See
TracTickets for help on using
tickets.
