From: Bryan Hundven <bryanhundven@gmail.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 5a5fcb: patches/gcc: Backport fix for building gcc-5 with ...
Date: Fri, 13 May 2016 21:33:00 -0000 [thread overview]
Message-ID: <573648308cabb_63ba3fd9996bf2bc449fa@hookshot-fe2-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 5a5fcbe148acf35372ecac145816c3515e6b8839
https://github.com/crosstool-ng/crosstool-ng/commit/5a5fcbe148acf35372ecac145816c3515e6b8839
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-05-13 (Fri, 13 May 2016)
Changed paths:
A patches/gcc/5.3.0/130-build_gcc-5_with_gcc-6.patch
Log Message:
-----------
patches/gcc: Backport fix for building gcc-5 with gcc-6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69959
...was observed while trying to build gcc-5.3.0 on latest (at the time
of this change) archlinux using gcc-6.1.1.
This patch fixes the issue.
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Commit: 7300eb17b43a38320d25dff47230f483a82b4154
https://github.com/crosstool-ng/crosstool-ng/commit/7300eb17b43a38320d25dff47230f483a82b4154
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-05-13 (Fri, 13 May 2016)
Changed paths:
A patches/gcc/5.3.0/130-build_gcc-5_with_gcc-6.patch
Log Message:
-----------
Merge pull request #392 from bhundven/fix_building_gcc-5_with_gcc-6
patches/gcc: Backport fix for building gcc-5 with gcc-6
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/cd39285ff824...7300eb17b43a
[-- Attachment #2: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2016-05-13 21:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 21:33 Bryan Hundven [this message]
[not found] ` <CAF+MRtmLOjR_orv6tLe5Mj8B7BKdPkxaNVvfzk+Duvs2xdzefQ@mail.gmail.com>
[not found] ` <662BF64F-6357-482A-87EE-92061E0ECC57@gmail.com>
2016-05-14 11:47 ` Micka
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=573648308cabb_63ba3fd9996bf2bc449fa@hookshot-fe2-cp1-prd.iad.github.net.mail \
--to=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).