From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 2/2] package/gcc: fix build of gcc-7.3.0 with glibc-2.28
Date: Sun, 12 Aug 2018 20:10:34 +0200 [thread overview]
Message-ID: <qp964fxkpu.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20180812194851.37f58885@windsurf
Hi Thomas,
Am Sun, 12 Aug 2018 19:48:51 +0200 schrieb Thomas Petazzoni:
> What about the older gcc versions we support ?
upstream has no patches for these versions:
> 4.9.4
https://gcc.gnu.org/git/?p=gcc.git;a=history;f=libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc;h=196eb3b3c6458b30c2b1a47e0d5ef514b3063044;hb=refs/heads/gcc-4_9-branch
> 5.5.0
https://gcc.gnu.org/git/?p=gcc.git;a=history;f=libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc;h=0d5b11f6e15f55a3193ced0f329461c9b9633185;hb=refs/heads/gcc-5-branch
> 6.4.0
https://gcc.gnu.org/git/?p=gcc.git;a=history;f=libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc;h=6992f2cd8ac56bcd5102f7440d71137b4458871d;hb=refs/heads/gcc-6-branch
> or1k-musl-5.4.0-20170218
Could not find an upstream branch at gcc.gnu.org.
Regards, Bernd
next prev parent reply other threads:[~2018-08-12 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-12 17:29 [Buildroot] [PATCH/next 1/2] package/gcc: renumber patch Bernd Kuhls
2018-08-12 17:29 ` [Buildroot] [PATCH/next 2/2] package/gcc: fix build of gcc-7.3.0 with glibc-2.28 Bernd Kuhls
2018-08-12 17:48 ` Thomas Petazzoni
2018-08-12 18:10 ` Bernd Kuhls [this message]
[not found] ` <ae19c065-5ce3-a333-173d-388612659cc3@t-online.de>
2018-08-12 19:04 ` [Buildroot] [PATCH/next 2/2] package/gcc: fix build of gcc-7.3.0 with Thomas Petazzoni
2018-08-13 18:17 ` Bernd Kuhls
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=qp964fxkpu.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--cc=buildroot@busybox.net \
/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