On 4/18/07, Charles R Harris <[EMAIL PROTECTED]> wrote: > On 4/18/07, Keith Goodman <[EMAIL PROTECTED]> wrote: > > I'd like to compile atlas so that I can take full advantage of my core > > 2 duo. Numpy dynamically links to the debian binary of atlas-sse that > > I installed. But the atlas website says that they recommend static > > linking. > > > > Which do you recommend, static or dynamic? Are there good directions for > either? > > I don't know which is best, although I suspect the statically linked version > will be larger. It might seem that just pulling in the gemm routines > wouldn't add much, but they pull in lots of supporting routines. To get > numpy to link statically you will also probably need to have a directory > that contains only the *.a versions because the linker will default to the > *.so if they are present; i don't think there is a way to specify the > -static flag to the gcc compiler. Maybe someone else knows how to do that. > For ATLAS, I believe the latest versions are also recommended because the > stable version is so old.
At the moment best is equal to easiest since I have never compiled atlas. Does anyone know of a howto on compiling atlas (dynamically linked)? Besides speed I'm also interested in seeing if I can get rid of the repeatability problems I have with the debian atlas-sse2 binary. (Repeated calulations, as discuss on this list, give give difference results in numpy but not octave.) _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion