From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 8.2.0/gentoo/
Date: Thu, 18 Oct 2018 20:40:50 +0000 (UTC) [thread overview]
Message-ID: <1539895209.455a1ff3dbd5c06aa8987bfed050fd802ed34607.slyfox@gentoo> (raw)
commit: 455a1ff3dbd5c06aa8987bfed050fd802ed34607
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Thu Oct 18 20:40:09 2018 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Thu Oct 18 20:40:09 2018 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=455a1ff3
8.2.0: update 105_all_libgfortran-Werror.patch to include configure.ac
Before this change only configure was update, but not configure.ac.
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
8.2.0/gentoo/105_all_libgfortran-Werror.patch | 7 +++++++
8.2.0/gentoo/README.history | 1 +
2 files changed, 8 insertions(+)
diff --git a/8.2.0/gentoo/105_all_libgfortran-Werror.patch b/8.2.0/gentoo/105_all_libgfortran-Werror.patch
index c54a469..f6c26bf 100644
--- a/8.2.0/gentoo/105_all_libgfortran-Werror.patch
+++ b/8.2.0/gentoo/105_all_libgfortran-Werror.patch
@@ -4,6 +4,13 @@ https://bugs.gentoo.org/433435
http://gcc.gnu.org/PR54724
+--- a/libgfortran/configure.ac
++++ b/libgfortran/configure.ac
+@@ -140,3 +140,3 @@ AM_PROG_CC_C_O
+ if test "x$GCC" = "xyes"; then
+- AM_FCFLAGS="-I . -Wall -Werror -fimplicit-none -fno-repack-arrays -fno-underscoring"
++ AM_FCFLAGS="-I . -Wall -fimplicit-none -fno-repack-arrays -fno-underscoring"
+ ## We like to use C11 and C99 routines when available. This makes
--- a/libgfortran/configure
+++ b/libgfortran/configure
@@ -5764,3 +5764,3 @@ fi
diff --git a/8.2.0/gentoo/README.history b/8.2.0/gentoo/README.history
index d85e258..3a021b7 100644
--- a/8.2.0/gentoo/README.history
+++ b/8.2.0/gentoo/README.history
@@ -1,5 +1,6 @@
1.5 TODO
+ 111_all_ubd-hog-PR85704.patch
+ U 105_all_libgfortran-Werror.patch
1.4 01 Oct 2018
+ 105_all_libgfortran-Werror.patch
next reply other threads:[~2018-10-18 20:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 20:40 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-08 22:42 [gentoo-commits] proj/gcc-patches:master commit in: 8.2.0/gentoo/ Sergei Trofimovich
2019-02-11 21:59 Sergei Trofimovich
2019-02-10 12:12 Sergei Trofimovich
2019-01-29 20:24 Sergei Trofimovich
2018-12-26 19:31 Sergei Trofimovich
2018-12-18 22:38 Sergei Trofimovich
2018-12-10 22:48 Sergei Trofimovich
2018-12-01 13:06 Sergei Trofimovich
2018-11-22 23:55 Sergei Trofimovich
2018-10-27 9:04 Sergei Trofimovich
2018-10-21 9:24 Sergei Trofimovich
2018-10-20 9:40 Sergei Trofimovich
2018-10-08 22:05 Sergei Trofimovich
2018-10-08 22:05 Sergei Trofimovich
2018-10-01 6:41 Sergei Trofimovich
2018-09-30 22:08 Sergei Trofimovich
2018-09-23 20:37 Sergei Trofimovich
2018-09-15 19:30 Sergei Trofimovich
2018-08-12 22:56 Sergei Trofimovich
2018-08-12 20:27 Sergei Trofimovich
2018-08-08 8:37 Sergei Trofimovich
2018-08-08 8:31 Sergei Trofimovich
2018-08-08 8:26 Sergei Trofimovich
2018-08-08 7:58 Sergei Trofimovich
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=1539895209.455a1ff3dbd5c06aa8987bfed050fd802ed34607.slyfox@gentoo \
--to=slyfox@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