From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 1/3] package/clapack: introduce BR2_PACKAGE_CLAPACK_ARCH_SUPPORTS
Date: Sun, 25 Jul 2021 09:47:49 +0200 [thread overview]
Message-ID: <20210725074749.GO2382418@scaer> (raw)
In-Reply-To: <20210724214526.47637-1-arnout@mind.be>
Arnout, All,
On 2021-07-24 23:45 +0200, Arnout Vandecappelle (Essensium/Mind) spake thusly:
> This makes it easier for packages that depend on clapack to get
> their dependencies correct.
>
> Since the glibc dependency only exists for PowerPC, treat it as
> an architecture dependency.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/clapack/Config.in | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/package/clapack/Config.in b/package/clapack/Config.in
> index a912eb6c91..98f94b0e60 100644
> --- a/package/clapack/Config.in
> +++ b/package/clapack/Config.in
> @@ -1,14 +1,19 @@
> +config BR2_PACKAGE_CLAPACK_ARCH_SUPPORTS
> + bool
> + default y
> + # assembler: Error: value out of range
> + depends on !BR2_m68k_cf
> + # _fpu_control is used on PowerPC, but not available with
> + # uClibc or musl
> + depends on !BR2_powerpc || BR2_TOOLCHAIN_USES_GLIBC
> +
> comment "clapack needs a glibc toolchain"
> depends on BR2_powerpc
> depends on !BR2_TOOLCHAIN_USES_GLIBC
>
> config BR2_PACKAGE_CLAPACK
> bool "cblas/clapack"
> - # _fpu_control is used on PowerPC, but not available with
> - # uClibc or musl
> - depends on !BR2_powerpc || BR2_TOOLCHAIN_USES_GLIBC
> - # assembler: Error: value out of range
> - depends on !BR2_m68k_cf
> + depends on BR2_PACKAGE_CLAPACK_ARCH_SUPPORTS
> help
> BLAS and LAPACK C implementation (f2c'ed version of).
>
> --
> 2.31.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-07-25 7:48 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
2021-07-25 7:47 ` Yann E. MORIN [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=20210725074749.GO2382418@scaer \
--to=yann.morin.1998@free.fr \
--cc=arnout@mind.be \
--cc=buildroot@buildroot.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox