public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michael Orlitzky" <mjo@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/mumps/
Date: Tue,  7 Sep 2021 17:56:42 +0000 (UTC)	[thread overview]
Message-ID: <1631037281.c6902b80403a506ebe337818c849f7d468294927.mjo@gentoo> (raw)

commit:     c6902b80403a506ebe337818c849f7d468294927
Author:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
AuthorDate: Tue Sep  7 17:53:50 2021 +0000
Commit:     Michael Orlitzky <mjo <AT> gentoo <DOT> org>
CommitDate: Tue Sep  7 17:54:41 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c6902b80

sci-libs/mumps: new revision to fix more underlinking.

When building without USE=mpi, the various lib*mumps libraries use
LAPACK symbols without actually linking to liblapack. There are
already a bunch of hacks in the mumps ebuild to work around these
issues, so all I've done is add one more. As a simple test case,
you can try to run the test suite for sci-libs/coinor-clp with
USE="mumps metis", which now works.

Closes: https://bugs.gentoo.org/777840
Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Michael Orlitzky <mjo <AT> gentoo.org>

 sci-libs/mumps/{mumps-5.3.5.ebuild => mumps-5.3.5-r1.ebuild} | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/sci-libs/mumps/mumps-5.3.5.ebuild b/sci-libs/mumps/mumps-5.3.5-r1.ebuild
similarity index 97%
rename from sci-libs/mumps/mumps-5.3.5.ebuild
rename to sci-libs/mumps/mumps-5.3.5-r1.ebuild
index 76f2dbe8d4d..8f970661e82 100644
--- a/sci-libs/mumps/mumps-5.3.5.ebuild
+++ b/sci-libs/mumps/mumps-5.3.5-r1.ebuild
@@ -25,6 +25,7 @@ RDEPEND="
 		mpi? ( >=sci-libs/parmetis-4 )
 	)
 	mpi? ( sci-libs/scalapack )
+	!mpi? ( virtual/lapack )
 	scotch? ( >=sci-libs/scotch-6.0.1:=[mpi=] )
 "
 DEPEND="${RDEPEND}"
@@ -83,6 +84,8 @@ src_prepare() {
 }
 
 src_configure() {
+	# We abuse LIBADD here to work around the fact that MUMPS is criminally
+	# underlinked.
 	LIBADD="$($(tc-getPKG_CONFIG) --libs blas) -Llib -lpord"
 	local ord="-Dpord"
 
@@ -132,6 +135,7 @@ src_configure() {
 			-e "s;^\(SCALAP\s*=\).*;\1;" \
 			-e 's;^LIBSEQNEEDED =;LIBSEQNEEDED = libseqneeded;g' \
 			Makefile.inc || die
+		LIBADD="${LIBADD} $($(tc-getPKG_CONFIG) --libs lapack)"
 		export LINK="$(tc-getFC)"
 	fi
 	sed -i -e "s;^\s*\(ORDERINGSF\s*=\).*;\1 ${ord};" Makefile.inc || die


             reply	other threads:[~2021-09-07 17:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 17:56 Michael Orlitzky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-21  5:58 [gentoo-commits] repo/gentoo:master commit in: sci-libs/mumps/ Sam James
2024-03-21  3:16 Sam James
2023-03-07  0:18 Yixun Lan
2023-01-02 18:42 Matthias Maier
2022-12-04  9:23 WANG Xuerui
2021-04-07  5:24 Sam James
2021-04-07  5:24 Sam James
2021-01-02  7:02 Sam James
2021-01-02  7:02 Sam James
2021-01-02  7:02 Sam James
2020-09-18 22:27 Sam James
2020-09-18 16:58 Sam James
2020-09-18 16:47 Sam James
2020-09-18 16:47 Sam James
2018-11-26  0:36 Matthias Maier
2018-11-26  0:36 Matthias Maier
2018-11-26  0:31 Matthias Maier
2018-10-08 17:56 Matthias Maier

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=1631037281.c6902b80403a506ebe337818c849f7d468294927.mjo@gentoo \
    --to=mjo@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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