![](https://secure.gravatar.com/avatar/054716f6af4fd585964570ef36de01a4.jpg?s=120&d=mm&r=g)
After experiencing a bit of difficulty to get everything {ATLAS,LAPACK,F2PY,Numeric,SciPy} working, I wrote this little script to automate the process for nodes on a cluster. I guess it can serve as a quick & dirty how-to for other newcomers. I used downloads from a local-network machine, just uncomment the original locations, etc. Feel free to use and redistribute it however you like. Regards, Louis. -------------------------------------------------------------- Louis Cordier, c:+27721472305, h:+27218865145, w:+27218084315 lcordier@dsp.sun.ac.za, http://www.dsp.sun.ac.za/~lcordier/ University of Stellenbosch - Electric & Electronic Engineering --------------------------------------------------------------
![](https://secure.gravatar.com/avatar/606c6b30649a819832da296039ab3e6c.jpg?s=120&d=mm&r=g)
"LC" == Louis Cordier <lcordier@dsp.sun.ac.za> writes:
LC> After experiencing a bit of difficulty to get everything LC> {ATLAS,LAPACK,F2PY,Numeric,SciPy} working, I wrote this little LC> script to automate the process for nodes on a cluster. I guess LC> it can serve as a quick & dirty how-to for other newcomers. LC> I used downloads from a local-network machine, just uncomment LC> the original locations, etc. Feel free to use and redistribute LC> it however you like. Nice. I am not sure you need to build lapack from source. I've used the standard debian lapack-dev and it seems to work ok. Also I notice that you stick the ATLAS stuff in /usr/lib/atlas which is not the right thing to do. I think /usr/local/lib/atlas is better. cheers, prabhu
participants (2)
-
Louis Cordier
-
Prabhu Ramachandran