all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: OpenBLAS
Date: Sun, 9 Oct 2016 12:19:18 +0000	[thread overview]
Message-ID: <20161009121918.GA5567@mail.thebird.nl> (raw)
In-Reply-To: <CAKrPhPPKRYi3AGB=VOCdwb-p9bZ7=NTOjR3TLaXKNmBdpWOSGw@mail.gmail.com>

On Sat, Oct 08, 2016 at 10:13:39PM +0200, Federico Beffa wrote:
> Hi,
> 
> I'm wondering why our OpenBLAS package is built with the flag
> "NO_LAPACK=1". It is my understanding that with this optional flag
> OpenBLAS doesn't include LAPACK, while without this flag and by
> default it does include the LAPACK functions.  In the latter case
> OpenBLAS could be used by a larger number of packages which do require
> LAPACK functions.
> 
> https://github.com/xianyi/OpenBLAS/issues/203

NO_LAPACK=0 does not use external libs. NO_LAPACK=1 uses external
liblapack. They both cover LAPACK functionality.

NO_LAPACK=1 is the conservative choice - it still is what most
software has been developed against today.

OpenBLAS has merged LAPACK code and they have been changing things,
claiming their version is better performing. But since it is less well
tested, new bugs are quite possible. I have hit at least one OpenBLAS
bug, so far.

Personally I think we should have both options in Guix, but we should
probably keep defaulting to NO_LAPACK=1.

Pj.

  reply	other threads:[~2016-10-09 12:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-08 20:13 OpenBLAS Federico Beffa
2016-10-09 12:19 ` Pjotr Prins [this message]
2016-10-09 18:02   ` OpenBLAS Federico Beffa

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=20161009121918.GA5567@mail.thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.