From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Cc: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v5 3/3] package/armadillo: allow to select between lapack or openblas
Date: Tue, 3 Aug 2021 22:55:42 +0200 [thread overview]
Message-ID: <20210803225542.442262e6@windsurf> (raw)
In-Reply-To: <20210725111231.359830-3-arnout@mind.be>
On Sun, 25 Jul 2021 13:12:31 +0200
"Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be> wrote:
> From: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
>
> armadillo can use lapack or openblas as BLAS provider. LAPACK support is
> optional.
>
> This patch
> - adds an _ARCH_SUPPORTS variable to check if one is available
> - adds an option to choose lapack or openblas as BLAS provider
>
> The choice is required since applications may potentially need lapack.
>
> Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> Changes v4 -> v5: [Done by Arnout]
> - Consistent naming of BR2_PACKAGE_ARMADILLO_OPENBLAS (Yann E. Morin)
> - Remove double dependency on lapack/clapack (Yann E. Morin)
> - Remove stray 'endchoice'
> - "Solve" circular dependency by removing clapack
> Changes v3 -> v4: [Done by Arnout]
> - Split off lapack/clapack arch depends in separate patches
> - Simplify the comments (no need for the powerpc complexity)
> - Remove the choices because clapack/lapack choice doesn't work. Keep a
> single config for openblas.
> Changes v2 -> v3:
> - drop all default statements for choice (Thomas)
> - add explicit -l since blas libary is called liblas for (c)lapack and
> libopenblas for openblas (Thomas)
> - add a choice for lapack selection between lapack, clapack or none
> Changes v1 -> v2:
> - add openblas as blas provider
> ---
> package/armadillo/Config.in | 34 ++++++++++++++++++++++++++--------
> package/armadillo/armadillo.mk | 18 +++++++++++++++++-
> 2 files changed, 43 insertions(+), 9 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-03 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 11:12 [Buildroot] [PATCH v5 1/3] package/python-numpy: use lapack instead of clapack Arnout Vandecappelle (Essensium/Mind)
2021-07-25 11:12 ` [Buildroot] [PATCH v5 2/3] package/clapack: Remove Arnout Vandecappelle (Essensium/Mind)
2021-07-26 21:47 ` Thomas Petazzoni
2021-07-25 11:12 ` [Buildroot] [PATCH v5 3/3] package/armadillo: allow to select between lapack or openblas Arnout Vandecappelle (Essensium/Mind)
2021-07-25 15:57 ` Gwenhael Goavec-Merou
2021-07-26 6:24 ` Arnout Vandecappelle
2021-07-27 13:49 ` Gwenhael Goavec-Merou
2021-08-03 20:57 ` Thomas Petazzoni
2021-08-03 21:49 ` Arnout Vandecappelle
2021-08-03 20:55 ` Thomas Petazzoni [this message]
2021-07-26 21:47 ` [Buildroot] [PATCH v5 1/3] package/python-numpy: use lapack instead of clapack Thomas Petazzoni
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=20210803225542.442262e6@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.org \
--cc=gwenhael.goavec-merou@trabucayre.com \
/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