[lsst-dm-stack-users] [LSST-data] Fail to newinstall.sh on MacOS 10.8: doxygen: eups: command not found (fwd)

[Dustin Lang]

Aha, I found out what my problem was.

In my ~/.bashrc I set BASH_ENV=~/.bashrc, and in ~/.bashrc I reset PATH, 
PYTHONPATH, and some other variables.  To remind you, $BASH_ENV, if it 
exists, is the startup script read by non-interactive bash shells (ie, 
when running shell scripts).

As a result, commands like this fail, because the shell script runs in a 
new shell, and my ~/.bashrc destroys the carefully setup environment:

source /usr/lsst/eups/bin/setups.sh; export EUPS_PATH=/usr/lsst; (/usr/lsst/EupsBuildDir/DarwinX86/scons-2.1.0+7/build.sh)

I believe a fix would be to suggest that users:

unset BASH_ENV

before running newinstall.sh.

For me, this results in a successful run from a clean directory.

Thanks again to everyone for their help, and my apologies for the trouble.

--dustin


On Wed, 25 Jun 2014, Dustin Lang wrote:

> 
> Hmm, well, I added /usr/lsst/eups/bin to my PATH in ~/.bashrc, and 
> newinstall.sh now manages to install doxygen.  scons fails, but that's 
> another email...
> 
> Thanks for everyone's responses.
> 
> --dustin
> 
> On Tue, 24 Jun 2014, Kian-Tat Lim wrote:
> 
> > Dustin,
> > 
> > > + eups list -s
> > > /usr/lsst/EupsBuildDir/DarwinX86/doxygen-1.8.2+2/build.sh: line 37: eups: 
> > > command not found
> > 
> > 	This isn't always because it can't find eups; it may be because
> > it can't find the interpreter that eups is using in the #! line (could
> > potentially be env, sh, or python).
> > 
> > -- 
> > Kian-Tat Lim, LSST Data Management, ktl at slac.stanford.edu
> > 
>