public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergey Torokhov" <torokhov-s-a@yandex.ru>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: sci-physics/SU2/
Date: Sun, 24 Oct 2021 21:07:15 +0000 (UTC)	[thread overview]
Message-ID: <1635109557.584e239fa636150d6680c82fb0a21c7a764ba650.SergeyTorokhov@gentoo> (raw)

commit:     584e239fa636150d6680c82fb0a21c7a764ba650
Author:     Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
AuthorDate: Sun Oct 24 20:56:36 2021 +0000
Commit:     Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
CommitDate: Sun Oct 24 21:05:57 2021 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=584e239f

sci-physics/SU2: restrict with MPI 3.1 impl. Add custom-mpi option

Meson.build script isn't properly detect mpich as MPI impl.,
therefore meson option 'custom-mpi' is used now with export
of CC=mpicc and CXX=mpicxx as compilers.

Mpi implementations is restricted with MPI 3.1 within ebuild.

FEATURES="-network-sandbox" could be required to run tests
for some mpi implementations/versions.

Closes: https://bugs.gentoo.org/819060

Signed-off-by: Sergey Torokhov <torokhov-s-a <AT> yandex.ru>

 sci-physics/SU2/SU2-7.2.0.ebuild | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/sci-physics/SU2/SU2-7.2.0.ebuild b/sci-physics/SU2/SU2-7.2.0.ebuild
index 7b3091907..32027c04f 100644
--- a/sci-physics/SU2/SU2-7.2.0.ebuild
+++ b/sci-physics/SU2/SU2-7.2.0.ebuild
@@ -35,7 +35,7 @@ REQUIRED_USE="
 
 RDEPEND="
 	${PYTHON_DEPS}
-	mpi? ( virtual/mpi[cxx] )
+	mpi? ( || ( >=sys-cluster/openmpi-1.10.7[cxx] >=sys-cluster/mpich-3.3[cxx] ) )
 	mkl? ( sci-libs/mkl )
 	openblas? ( sci-libs/openblas )
 "
@@ -87,6 +87,11 @@ src_prepare(){
 }
 
 src_configure() {
+	if use mpi ; then
+		export CC=mpicc
+		export CXX=mpicxx
+	fi
+
 	local emesonargs=(
 		-Denable-autodiff=false
 		-Denable-directdiff=false
@@ -94,6 +99,7 @@ src_configure() {
 		-Denable-pywrapper=false
 		-Dwith-omp=false
 		$(meson_feature mpi with-mpi)
+		$(meson_use mpi custom-mpi)
 		$(meson_use cgns enable-cgns)
 		$(meson_use mkl enable-mkl)
 		$(meson_use mpp enable-mpp)


             reply	other threads:[~2021-10-24 21:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24 21:07 Sergey Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-23 10:44 [gentoo-commits] repo/proj/guru:dev commit in: sci-physics/SU2/ Sergey Torokhov
2023-04-23  9:48 Sergey Torokhov
2022-12-09 16:52 Sergey Torokhov
2022-12-09 16:52 Sergey Torokhov
2022-12-08 22:44 Sergey Torokhov
2022-05-28 13:45 Alessandro Barbieri
2021-10-27 20:55 Sergey Torokhov
2021-10-15 16:20 Sergey Torokhov
2021-09-15 21:43 Sergey Torokhov
2021-09-05 10:45 Sergey Torokhov
2021-08-31 14:07 Sergey Torokhov
2021-08-31 14:07 Sergey Torokhov
2021-05-30 15:59 [gentoo-commits] repo/proj/guru:master " Andrew Ammerlaan
2021-05-30 15:59 ` [gentoo-commits] repo/proj/guru:dev " Andrew Ammerlaan
2021-03-28 10:52 Andrew Ammerlaan
2021-03-22 20:14 Sergey Torokhov
2021-03-10 20:02 Sergey Torokhov
2021-01-05 14:00 Sergey Torokhov
2021-01-05 13:54 Sergey Torokhov

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=1635109557.584e239fa636150d6680c82fb0a21c7a764ba650.SergeyTorokhov@gentoo \
    --to=torokhov-s-a@yandex.ru \
    --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