On Tuesday, July 5, 2016 at 7:33:50 PM UTC+1, tdumont wrote: > > Le 04/07/2016 23:10, Francois Bissey a écrit : > > I wouldn’t try to use one of these. Detecting blas/lapack automatically > is > > a fool’s errand. There are no standard naming scheme for the libraries > > and distress can mess things up on top of it. > > The only safe way is to get the stuff needed to link on the command > line. > > You may want to add detection of the fortran mangling, that suppose you > > will be making your code able to cope with that too. > > > > > Not sure... > > I am a cmake user; I do not propose to include cmake in sage :-), but > cmake comes with a lot of scripts like FindBLAS.cmake and FindLAPACK.cmake >
cmake is a Sage experimental package, in fact... > > I have used them on many linux distributions and it always worked. > > So it is certainly possible to mimic what cmake is doing, say with a > python script. Maybe it already exists... > > t.d. > > > However I would like to know more about the particular lapack install > > you are trying to detect: > > 1) is it in /usr/lib(64) or /usr/local/lib? > > 2) is it all shared object or static [the way you look at gfortran, blas > and then > > lapack, suggests static] > > > > François > > > > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
