From: "Justin Lecher" <jlec@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sci:master commit in: sci-libs/nexus/
Date: Thu, 22 Jan 2015 10:14:20 +0000 (UTC) [thread overview]
Message-ID: <1421789012.d5e2245ffa5d0632b79ed33ab39acfc91b40944e.jlec@gentoo> (raw)
commit: d5e2245ffa5d0632b79ed33ab39acfc91b40944e
Author: Chris Kerr <debdepba <AT> dasganma <DOT> tk>
AuthorDate: Tue Jan 20 21:23:32 2015 +0000
Commit: Justin Lecher <jlec <AT> gentoo <DOT> org>
CommitDate: Tue Jan 20 21:23:32 2015 +0000
URL: http://sources.gentoo.org/gitweb/?p=proj/sci.git;a=commit;h=d5e2245f
export MAKEOPTS in pkg_setup so we can use the default src_compile
---
sci-libs/nexus/nexus-4.3.1.ebuild | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/sci-libs/nexus/nexus-4.3.1.ebuild b/sci-libs/nexus/nexus-4.3.1.ebuild
index 22c81d4..e887f03 100644
--- a/sci-libs/nexus/nexus-4.3.1.ebuild
+++ b/sci-libs/nexus/nexus-4.3.1.ebuild
@@ -33,6 +33,8 @@ DEPEND="${RDEPEND}
pkg_setup() {
use python && python-single-r1_pkg_setup
+ # Handling of dependencies between Fortran module files doesn't play well with parallel make
+ use fortran && export MAKEOPTS="${MAKEOPTS} -j1 "
use fortran && fortran-2_pkg_setup
}
@@ -50,9 +52,3 @@ src_configure() {
$(use_with java) \
$(use_with python)
}
-
-src_compile() {
- # Handling of dependencies between Fortran module files doesn't play well with parallel make
- use fortran && MAKEOPTS="${MAKEOPTS} -j1 "
- default
-}
next reply other threads:[~2015-01-22 10:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 10:14 Justin Lecher [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-22 10:14 [gentoo-commits] proj/sci:master commit in: sci-libs/nexus/ Justin Lecher
2015-01-22 10:14 Justin Lecher
2015-09-21 19:05 Justin Lecher
2016-01-10 15:32 Justin Lecher
2016-01-10 15:32 Justin Lecher
2016-01-10 15:32 Justin Lecher
2016-01-10 15:32 Justin Lecher
2016-01-10 15:32 Justin Lecher
2020-09-28 0:46 Aisha Tammy
2020-09-28 0:46 Aisha Tammy
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=1421789012.d5e2245ffa5d0632b79ed33ab39acfc91b40944e.jlec@gentoo \
--to=jlec@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