[lsst-dm-stack-users] adding scipy to DMstack installation

[Mario Juric]

On 4/2/13 13:33 , Heather Kelly wrote:
> 
> I'm now trying to do a similar thing for our RHEL5-64 installation which
> was from the binaries you guys provided back in December...initially
> doing the eups distrib install --nolocks scipy failed, since it couldn't
> find blas or lapack - I did manage to point at our local installation of
> those.  Now it's failing since the link path is likely using the
> location of the python used when the binaries were created.  Is there a
> sensible way to add scipy in this case?  We don't have gcc44 for
> RHEL5-64 here so the binary installation seemed the best bet in this case.
> 

Heather,
	I think you'll need gcc44 RPM to get this built right. You may also
need to have the stack in /opt/lsst/rhel-5-x86_64.

	However, I built scipy for RHEL5 and added it to our binary
distribution server. Install blas and lapack RHEL5 RPMs, and then update
your stack with:

	setup lsst_distrib_tool
	lsst-distrib update

and you should have scipy.

*** WARNING ****: the update process will remove all customizations
(e.g., additional packages that you may have installed manually). The
only way to avoid this right now is to hack the lsst-distrib binary and
remove '--delete' switch from the rsync call. I'd recommended to build
site-specific packages in a different directory (I can send more info on
how to do this if needed).

PS: Whatever you do, just to be safe, back up the stack directory before
running the update :).

If this works well, I'll build scipy binaries for other platforms.

Cheers,
-- 
Mario Juric,
Data Mgmt. Project Scientist, Large Synoptic Survey Telescope
Web   :  http://www.cfa.harvard.edu/~mjuric/
Phone :  +1 617 744 9003       PGP: ~mjuric/crypto/public.key