Hi Danny!
On Saturday 07 May 2005 7:57 pm, Danny van Dyk wrote:
> Hi Darren,
>
> > I thought I might try to get some work done on a few science-related
> > python packages. A reminder of what was at issue:
>
> I'm really sorry to have forgotten you and your BUG. I've been a bit
> busy with my studies. You should have poked me earlier in regard to this
> per mail ;-) I need poking or I get distracted :-/
No problem. I didn't want to poke to much, I have been told that I sometimes
(unintentionally) come across as pushy through email.
>
> > Numeric, numarray and scipy all have the ability to link to blas,lapack
> > and atlas libraries. By default, numeric and numarray will build against
> > their own internal, and slower, libraries.
> >
> > I had submitted an ebuild for Numeric which, if USE=atlas, modified the
> > install script to link to the libraries provided by lapack-atlas (and its
> > dependency, blas-atlas), and made lapack-atlas a dependency. One of the
> > devs improved upon my initial offering, suggesting that they were no
> > longer using the atlas use flag, and changed the dependency to virtual
> > lapack.
>
> Back to this, i had to modify the build a little more and i dropped your
> patch entirely in order to use sed. We need to use sed, as we have to
> set the library dir in setup.py. As this is lib64 on amd64 f.e, we have
> to use $(get_libdir) to refer to the right libdir. I have attached 2
> little patches against numeric-23.7 and numeric-23.8. They compile fine
> for me, and I'm now interested if you find any regressions. If they work
> for you, I'll add them to CVS ASAP (promised!!) :-)
I'll test it tomorrow.
>
> > Numeric, numarray, and scipy all need atlas specific information during
> > the build, if it is available. How can I get the atlas information into
> > the setup scripts, if it is appropriate to do so?
>
> You refer to cblas.h? I'll be adding it to numerics ${FILESDIR}, as
> cblas.h is licensed under BSD license. Legally, no problem ;-)
>
> > What happens if Numeric is built against lapack-atlas, and then I use
> > lapack-config to switch to MKL? Numeric would still be linked to
> > libatlas.*, is that a problem?
>
> No. Numeric is build against /usr/$(get_libdir)/liblapack.so, everytime.
> liblapack.so itself is a symlink to whatever you choose to let it point
> to. When you change that symlink to libfoo.so, numeric will use
> libfoo.so instead of ATLAS's liblapack.so.
>
I was more concerned about linking to /usr/lib/libatlas.*, and all the files
in /usr/include/atlas/. These are installed by lapack-atlas, and both Scipy
and Numeric will link to them if available.
Thanks,
Darren
--
Darren S. Dale
Bard Hall
Department of Materials Science and Engineering
Cornell University
Ithaca, NY. 14850
[EMAIL PROTECTED]
--
[email protected] mailing list
