public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Christoph Junghans" <ottxor@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-libs/p4est/
Date: Fri,  2 Sep 2016 22:08:55 +0000 (UTC)	[thread overview]
Message-ID: <1472764078.f6af5d93e2ecbed116c5a9aa35c86261d5ab67b1.ottxor@gentoo> (raw)

commit:     f6af5d93e2ecbed116c5a9aa35c86261d5ab67b1
Author:     Matthias Maier <tamiko <AT> gentoo <DOT> org>
AuthorDate: Thu Sep  1 21:05:06 2016 +0000
Commit:     Christoph Junghans <ottxor <AT> gentoo <DOT> org>
CommitDate: Thu Sep  1 21:07:58 2016 +0000
URL:        https://gitweb.gentoo.org/proj/sci.git/commit/?id=f6af5d93

sci-libs/p4est: add openmp and threads use flags

Package-Manager: portage-2.2.28

 sci-libs/p4est/p4est-9999.ebuild | 17 ++++++++++++++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/sci-libs/p4est/p4est-9999.ebuild b/sci-libs/p4est/p4est-9999.ebuild
index 05f4f1b..33c371d 100644
--- a/sci-libs/p4est/p4est-9999.ebuild
+++ b/sci-libs/p4est/p4est-9999.ebuild
@@ -26,16 +26,17 @@ fi
 LICENSE="GPL-2+"
 SLOT="0"
 
-IUSE="debug doc examples mpi romio static-libs +vtk-binary"
+# TODO petsc
+IUSE="debug doc examples mpi openmp romio static-libs threads +vtk-binary"
 REQUIRED_USE="romio? ( mpi )"
 
 RDEPEND="
-	>=sci-libs/libsc-1.0[mpi,romio]
+	>=sci-libs/libsc-1.0[mpi=,openmp=,romio=,threads=]
 	dev-lang/lua:*
 	sys-apps/util-linux
 	virtual/blas
 	virtual/lapack
-	mpi? ( virtual/mpi[romio?] )"
+	mpi? ( virtual/mpi[romio=] )"
 
 DEPEND="
 	${RDEPEND}
@@ -47,6 +48,13 @@ DOCS=( AUTHORS NEWS README )
 AT_M4DIR="${WORKDIR}/${P}/config ${WORKDIR}/${P}/sc/config"
 AUTOTOOLS_AUTORECONF=true
 
+pkg_pretend() {
+	if [[ ${MERGE_TYPE} != "binary" ]] && use openmp; then
+		tc-has-openmp || \
+			die "Please select an openmp capable compiler like gcc[openmp]"
+	fi
+}
+
 src_prepare() {
 	# Inject libsc to get  all parts of the build system...
 	if ! [[ ${PV} = *9999* ]]; then
@@ -76,10 +84,13 @@ src_configure() {
 	local myeconfargs=(
 		$(use_enable debug)
 		$(use_enable mpi)
+		$(use_enable openmp)
 		$(use_enable romio mpiio)
 		$(use_enable vtk-binary)
+		$(use_enable threads pthread)
 		--with-blas="$($(tc-getPKG_CONFIG) --libs blas)"
 		--with-lapack="$($(tc-getPKG_CONFIG) --libs lapack)"
+		$(use_with petsc)
 		--with-sc="${EPREFIX}/usr"
 	)
 	autotools-utils_src_configure


             reply	other threads:[~2016-09-02 22:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02 22:08 Christoph Junghans [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-02 22:08 [gentoo-commits] proj/sci:master commit in: sci-libs/p4est/ Christoph Junghans
2016-09-02 22:08 Christoph Junghans
2016-09-02 22:08 Christoph Junghans
2015-06-06 10:23 Justin Lecher
2015-06-06 10:23 Justin Lecher
2014-10-16 15:50 Christoph Junghans
2014-10-16 15:50 Christoph Junghans
2014-07-24 21:51 Jens-Malte Gottfried
2013-10-18 16:19 Christoph Junghans
2013-07-26 16:14 Nicolas Bock
2013-07-26 16:14 Nicolas Bock
2013-07-26 16:14 Nicolas Bock
2013-07-26 16:14 Nicolas Bock
2013-07-26 16:14 Nicolas Bock
2013-07-26 16:14 Nicolas Bock
2013-07-26 16:14 Nicolas Bock

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=1472764078.f6af5d93e2ecbed116c5a9aa35c86261d5ab67b1.ottxor@gentoo \
    --to=ottxor@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