From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 2/2] package/gcc: fix build of gcc-7.3.0 with
Date: Sun, 12 Aug 2018 21:04:19 +0200 [thread overview]
Message-ID: <20180812210419.78125b1e@windsurf> (raw)
In-Reply-To: <ae19c065-5ce3-a333-173d-388612659cc3@t-online.de>
Hello,
On Sun, 12 Aug 2018 20:10:43 +0200, Bernd Kuhls wrote:
> > What about the older gcc versions we support ?
>
> upstream has no patches for these versions:
Does this mean the problem doesn't exist, or just that the gcc
developers didn't backport the patch ?
Could you do a test build of gcc 6.x and glibc 2.28 ? Or perhaps verify
in the source code that the problem didn't exist back then ?
> > or1k-musl-5.4.0-20170218
>
> Could not find an upstream branch at gcc.gnu.org.
This is not an official upstream branch, but if the upstream 5.4.0 is
affected by the issue, the patch should apply just as well to this
branch.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-12 19:04 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
[not found] ` <ae19c065-5ce3-a333-173d-388612659cc3@t-online.de>
2018-08-12 19:04 ` Thomas Petazzoni [this message]
2018-08-13 18:17 ` [Buildroot] [PATCH/next 2/2] package/gcc: fix build of gcc-7.3.0 with 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=20180812210419.78125b1e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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