From: Charles R H. <cha...@gm...> - 2006-08-31 16:51:06
|
On 8/31/06, Christopher Barker <Chr...@no...> wrote: > > Jonathan Taylor wrote: > > When trying to install 1.0b4 I had trouble getting it to detect my > > installed atlas. This was because the shipped site.cfg had; > > > > [atlas] > > library_dirs = /usr/lib/atlas/3dnow/ > > atlas_libs = lapack, blas > > > > but I had to change 3dnow to sse2 due to my current state of > > pentiumness. In any case it should probabally look in all the > > possible locations instead of just AMD's location. > > "All possible locations" is pretty much impossible. There really isn't > any choice but for individuals to customize site.cfg for their setup. > that's why it's called "site".cfg. > > I would like to see a pretty good collection of examples, most of them > commented out, in there, however. i.e.: I need this on fc5 x86_64 [atlas] library_dirs = /usr/lib64/atlas atlas_libs = lapack, blas, cblas, atlas I think this should be automatic. Apart from debian, the /usr/lib64 directory is pretty much standard for 64bit linux distros. Chuck |