public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Olivier Cessenat <cessenat@orange.fr>
To: Patrick Alken <patrick.alken@Colorado.EDU>, gsl-discuss@sourceware.org
Subject: Re: Choice of an external blas lib
Date: Fri, 19 Mar 2021 21:26:20 +0100	[thread overview]
Message-ID: <0713c756-bd2a-a1f3-ed66-f1ad9952a8a8@orange.fr> (raw)
In-Reply-To: <5790211c-8bc8-ccda-266d-66d971155fd6@colorado.edu>

Ok, that's genious ! Thank you for explaining it to me, I had missed 
that point.

Just thinking aloud : so with spack that means the +external-cblas 
option is of no interest.

One can either [assuming depends_on('blas', when='+blas') and 
depends_on('gsl', when='+gsl')]

spack install mypackage+blas+gsl ^gsl ^myblas

or

spack install mypackage~blas+gsl ^gsl

with an internal spec:

<< mypackage/package.py : something like:

             if self.spec.satisfies('+gsl~blas'):
                 env.append_flags('LDLIBS', '-lgslcblas')

 >>

Cheers,

Olivier Cessenat

Le 19/03/2021 à 17:52, Patrick Alken a écrit :
> This is done at link time, not compile time. You can link your program
> with any cblas library of your choice
>
> On 3/19/21 3:29 AM, Olivier Cessenat wrote:
>> Dear GSL developers,
>>
>> If one of you could modify the configure script so that it becomes
>> easy to select an external cblas as has been done in "spack" for gsl
>> 2.3 to 2.5 it would be very nice.
>>
>> Thanks a lot,
>>
>> Olivier Cessenat
>>
>>
>>

      parent reply	other threads:[~2021-03-19 20:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  9:29 Olivier Cessenat
     [not found] ` <5790211c-8bc8-ccda-266d-66d971155fd6@colorado.edu>
2021-03-19 20:26   ` Olivier Cessenat [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0713c756-bd2a-a1f3-ed66-f1ad9952a8a8@orange.fr \
    --to=cessenat@orange.fr \
    --cc=gsl-discuss@sourceware.org \
    --cc=patrick.alken@Colorado.EDU \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).