All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aalx <alexandre.payen@smile.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/lapack: avoid selecting lapack and clapack
Date: Mon,  5 Aug 2019 12:35:18 +0200	[thread overview]
Message-ID: <20190805103518.8233-1-alexandre.payen@smile.fr> (raw)

From: Alexandre PAYEN <alexandre.payen@smile.fr>

lapack and clapack generate the same libraries liblapack.so and
libblas.so. So those two packages can't be selected at the same time.

This is a temporary fix waiting for a solution[2].

So:
- add !BR2_PACKAGE_CLAPACK to lapack/Config.in.

[1]: http://autobuild.buildroot.org/results/375/375078ed8f965ecf92eb9674bd071a518c3ef894//
[2]: http://lists.busybox.net/pipermail/buildroot/2019-August/255894.html

Signed-off-by: Alexandre PAYEN <alexandre.payen@smile.fr>
Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Cc: Romain Naour <romain.naour@smile.fr>
Cc: Thomas De Schampheleire <patrickdepinguin@gmail.com>
---
 package/lapack/Config.in | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package/lapack/Config.in b/package/lapack/Config.in
index 9687ace82d..6cd0810cb1 100644
--- a/package/lapack/Config.in
+++ b/package/lapack/Config.in
@@ -5,6 +5,7 @@ comment "lapack/blas needs a toolchain w/ fortran"
 config BR2_PACKAGE_LAPACK
 	bool "lapack/blas"
 	depends on BR2_TOOLCHAIN_HAS_FORTRAN
+	depends on !BR2_PACKAGE_CLAPACK
 	# _fpu_control is used on PowerPC, but not available with uClibc
 	depends on !(BR2_powerpc && BR2_TOOLCHAIN_USES_UCLIBC)
 	help
-- 
2.21.0

             reply	other threads:[~2019-08-05 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05 10:35 Aalx [this message]
2019-08-08 15:55 ` [Buildroot] [PATCH] package/lapack: avoid selecting lapack and clapack Romain Naour
2020-02-05 15:17 ` Arnout Vandecappelle
2020-03-10 21:28   ` Peter Korsgaard

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=20190805103518.8233-1-alexandre.payen@smile.fr \
    --to=alexandre.payen@smile.fr \
    --cc=buildroot@busybox.net \
    /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 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.