From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-cluster/mpich/
Date: Fri, 15 Oct 2021 22:01:41 +0000 (UTC) [thread overview]
Message-ID: <1634335280.2772ce712ccef6d9ae6196d5a84615d9c56b7811.sam@gentoo> (raw)
commit: 2772ce712ccef6d9ae6196d5a84615d9c56b7811
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 15 22:01:20 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Oct 15 22:01:20 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2772ce71
sys-cluster/mpich: add -fcommon for 3.0.4-r1
I can't reproduce this but it builds
with this anyway.
Closes: https://bugs.gentoo.org/818280
Signed-off-by: Sam James <sam <AT> gentoo.org>
sys-cluster/mpich/mpich-3.0.4-r1.ebuild | 3 +++
1 file changed, 3 insertions(+)
diff --git a/sys-cluster/mpich/mpich-3.0.4-r1.ebuild b/sys-cluster/mpich/mpich-3.0.4-r1.ebuild
index 08d63fd1943..8d5657d5993 100644
--- a/sys-cluster/mpich/mpich-3.0.4-r1.ebuild
+++ b/sys-cluster/mpich/mpich-3.0.4-r1.ebuild
@@ -85,6 +85,9 @@ src_configure() {
# dropped w/ bug #725842 fix
#unset CFLAGS CPPFLAGS CXXFLAGS FFLAGS FCFLAGS LDFLAGS
+ # Possible workaround for bug #818280
+ append-flags -fcommon
+
# Forcing Bash as there's quite a few bashisms in the build system
CONFIG_SHELL="${BROOT}/bin/bash" econf ${c} \
--with-pm=hydra \
next reply other threads:[~2021-10-15 22:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 22:01 Sam James [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 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-04-12 20:43 Justin Bronder
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=1634335280.2772ce712ccef6d9ae6196d5a84615d9c56b7811.sam@gentoo \
--to=sam@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