From: "Justin Bronder" <jsbronder@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-cluster/mpich/
Date: Wed, 12 Apr 2017 20:43:18 +0000 (UTC) [thread overview]
Message-ID: <1492029747.18ac817afbb862936e4c4aa3a46d15b7eddd9dae.jsbronder@gentoo> (raw)
commit: 18ac817afbb862936e4c4aa3a46d15b7eddd9dae
Author: Michael Gilroy <michael.gilroy24 <AT> gmail <DOT> com>
AuthorDate: Wed Apr 12 15:14:23 2017 +0000
Commit: Justin Bronder <jsbronder <AT> gentoo <DOT> org>
CommitDate: Wed Apr 12 20:42:27 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=18ac817a
sys-cluster/mpich: Fixed multilib_src_install() logic
Previously in the case where compiles used -fortran and
multilib_is_native_abi was true, the rm would fail and the build would
die. The nested conditional prevents this.
Bug: #612564
sys-cluster/mpich/mpich-3.2-r1.ebuild | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/sys-cluster/mpich/mpich-3.2-r1.ebuild b/sys-cluster/mpich/mpich-3.2-r1.ebuild
index 48ddf87a919..f862068a14d 100644
--- a/sys-cluster/mpich/mpich-3.2-r1.ebuild
+++ b/sys-cluster/mpich/mpich-3.2-r1.ebuild
@@ -101,13 +101,14 @@ multilib_src_install() {
default
# fortran header cannot be wrapped (bug #540508), workaround part 1
- if multilib_is_native_abi && use fortran; then
- mkdir "${T}"/fortran || die
- mv "${ED}"usr/include/mpif* "${T}"/fortran || die
- mv "${ED}"usr/include/*.mod "${T}"/fortran || die
- else
- # some fortran files get installed unconditionally
- rm "${ED}"usr/include/mpif* "${ED}"usr/include/*.mod || die
+ if use fortran; then
+ if multilib_is_native_abi; then
+ mkdir "${T}"/fortran || die
+ mv "${ED}"usr/include/mpif* "${T}"/fortran || die
+ mv "${ED}"usr/include/*.mod "${T}"/fortran || die
+ else
+ rm "${ED}"usr/include/mpif* "${ED}"usr/include/*.mod || die
+ fi
fi
}
next reply other threads:[~2017-04-12 20:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 20:43 Justin Bronder [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-16 1:52 [gentoo-commits] repo/gentoo:master commit in: sys-cluster/mpich/ Sam James
2023-01-12 21:50 Yixun Lan
2023-01-12 21:50 Yixun Lan
2022-01-12 9:41 Andreas Sturmlechner
2022-01-12 7:42 Agostino Sarubbo
2022-01-10 22:59 Sam James
2022-01-10 11:16 Arthur Zamarin
2022-01-10 11:14 Arthur Zamarin
2022-01-09 22:13 Andreas Sturmlechner
2021-12-18 8:08 Sam James
2021-12-18 8:08 Sam James
2021-10-29 22:44 Sam James
2021-10-15 22:01 Sam James
2021-10-15 21:43 Sam James
2021-10-13 5:26 Sam James
2021-10-13 5:12 Sam James
2021-09-23 20:36 Sam James
2021-09-23 20:31 Sam James
2020-12-21 19:34 Jonas Stein
2020-11-14 22:47 David Seifert
2019-09-04 14:21 Justin Bronder
2019-04-15 14:53 Justin Bronder
2018-09-21 13:42 Justin Bronder
2018-09-21 13:42 Justin Bronder
2018-06-11 10:51 Ulrich Müller
2017-06-23 19:26 Alexis Ballier
2017-04-15 13:08 Jeroen Roovers
2017-03-16 7:12 Michael Weber
2017-03-11 13:42 Agostino Sarubbo
2017-03-11 13:31 Agostino Sarubbo
2016-09-06 0:18 Christoph Junghans
2016-08-29 20:58 Christoph Junghans
2016-08-29 20:13 Christoph Junghans
2016-08-11 7:55 David Seifert
2015-12-21 13:54 Justin Bronder
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=1492029747.18ac817afbb862936e4c4aa3a46d15b7eddd9dae.jsbronder@gentoo \
--to=jsbronder@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