From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: 3.4.6/gentoo/
Date: Sat, 1 Jun 2019 10:01:40 +0000 (UTC) [thread overview]
Message-ID: <1559383203.4fc910bbdb638f7dc4c0cbc2eb560d5943a05cdb.slyfox@gentoo> (raw)
commit: 4fc910bbdb638f7dc4c0cbc2eb560d5943a05cdb
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Jun 1 10:00:03 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Jun 1 10:00:03 2019 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=4fc910bb
3.4.9: cut 1.9 patchset
Two new patches:
91_all_ucontext-to-ucontext_t.patch: fix libjava build on modern glibc
92_all_libtool-pass-all.patch: Unbreak libc and libm detection by libtool
when those are linker scripts.
Bug: https://bugs.gentoo.org/664486
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
3.4.6/gentoo/README.history | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/3.4.6/gentoo/README.history b/3.4.6/gentoo/README.history
index 15cf5c5..549063a 100644
--- a/3.4.6/gentoo/README.history
+++ b/3.4.6/gentoo/README.history
@@ -1,4 +1,4 @@
-1.9 [pending]
+1.9 1 Jun 2019
- 00_all_gcc-trampolinewarn.patch
+ 91_all_ucontext-to-ucontext_t.patch
+ 92_all_libtool-pass-all.patch
next reply other threads:[~2019-06-01 10:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-01 10:01 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-27 19:45 [gentoo-commits] proj/gcc-patches:master commit in: 3.4.6/gentoo/ Sergei Trofimovich
2019-10-21 22:16 Sergei Trofimovich
2019-06-15 19:11 Sergei Trofimovich
2019-06-15 19:01 Sergei Trofimovich
2019-06-12 21:30 Sergei Trofimovich
2018-11-30 7:37 Sergei Trofimovich
2018-09-30 12:27 Sergei Trofimovich
2018-09-29 20:31 Sergei Trofimovich
2018-09-16 16:10 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=1559383203.4fc910bbdb638f7dc4c0cbc2eb560d5943a05cdb.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