> On 2/12/2016, at 21:30, Jean-Pierre Flori <jpfl...@gmail.com> wrote: > > > > On Friday, December 2, 2016 at 9:24:16 AM UTC+1, François wrote: > > > On 2/12/2016, at 21:21, Thierry <sage-goo...@lma.metelu.net> wrote: > > > > Hi, > > > > the SAGE_ATLAS_LIB stuff, which allowed to use system blas belongs to > > SAGE_ROOT/build/pkgs/atlas/spkg-install Is it possible to have such option > > (perhaps renamed SAGE_BLAS_LIB) available even if openblas is selected as > > the default blas, or a specific (SAGE_OPENBLAS_LIB) one ? Would it be > > preferable to have this possibility dealt at configure time, not depending > > on Sage's default blas ? > > > > I am all for it, but we need a mechanism to generate appropriate .pc files > in that case. > Or couldn't we ask for a pointer to .pc file? > And copy it/use it inside Sage?
Manual all the way, eh? So “SYSTEM_BLAS_PC” pointing to pc files for blas, cblas and lapack. Difficulty, at least on OS X we cannot assume a system pkg-config to be present, so validation of pc file at configure time is of the menu - at least by invoking pkg-config. Francois -- 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.
