Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Romain Naour <romain.naour@gmail.com>,
	Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 3/3] package/armadillo: allows to select between clapack, lapack or openblas
Date: Sun, 25 Jul 2021 13:13:40 +0200	[thread overview]
Message-ID: <4e793690-349c-af33-e16c-b54489fdd1ff@mind.be> (raw)
In-Reply-To: <f3776222-ad4d-2d73-9bf7-a79b335d10f3@mind.be>



On 25/07/2021 11:36, Arnout Vandecappelle wrote:
>  I'll send a v5 which fixes it. I still want Gwenhael to confirm that it's good
> in this shape though.

 There won't be a v5 coming because I can't overcome the circular dependency.

 I think, actually, that we should just drop the clapack package. It's dead (the
lapack maintainers no longer generate clapack based on new lapack releases,
probably because f2c is unmaintained).

 I remember Romain and I were banging our heads against lapack, clapack and
openblas a couple of years ago on a Buildroot developer meeting - I believe it
was in the context of numpy at the time. I don't remember exactly what the
conclusion was, but IIRC there was no good solution at the time either.

 Well, in the end I went ahead and sent a v5 which removes clapack and
re-introduces the choice for BLAS provider. The "choice" for LAPACK provider is
automatic though (it's just yes or no anyway).

 Gwenhael, what do you think?


 Regards,
 Arnout
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2021-07-25 11:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 21:45 [Buildroot] [PATCH v4 1/3] package/clapack: introduce BR2_PACKAGE_CLAPACK_ARCH_SUPPORTS Arnout Vandecappelle (Essensium/Mind)
2021-07-24 21:45 ` [Buildroot] [PATCH v4 2/3] package/lapack: introduce BR2_PACKAGE_LAPACK_ARCH_SUPPORTS Arnout Vandecappelle (Essensium/Mind)
2021-07-25  7:47   ` Yann E. MORIN
2021-07-24 21:45 ` [Buildroot] [PATCH v4 3/3] package/armadillo: allows to select between clapack, lapack or openblas Arnout Vandecappelle (Essensium/Mind)
2021-07-25  7:57   ` Yann E. MORIN
2021-07-25  9:36     ` Arnout Vandecappelle
2021-07-25 11:13       ` Arnout Vandecappelle [this message]
2021-07-25  7:47 ` [Buildroot] [PATCH v4 1/3] package/clapack: introduce BR2_PACKAGE_CLAPACK_ARCH_SUPPORTS Yann E. MORIN

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=4e793690-349c-af33-e16c-b54489fdd1ff@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@buildroot.org \
    --cc=gwenhael.goavec-merou@trabucayre.com \
    --cc=romain.naour@gmail.com \
    --cc=yann.morin.1998@free.fr \
    /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