From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libgeos: fix build failure due to Gcc Bug 68485
Date: Mon, 15 Feb 2021 09:58:28 +0100 [thread overview]
Message-ID: <20210215095828.5584167d@windsurf.home> (raw)
In-Reply-To: <4164497f-c16c-99c9-e6e7-70e77c16c368@benettiengineering.com>
On Mon, 15 Feb 2021 00:46:35 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> > Applied to master, thanks. Could you check if this bug still exists
> > with gcc 10.x, and if it does, ping on the gcc bug report ?
>
> I've just tried to build with gcc 10.2 and unfortunately it still have
> that bug. So I've just pinged gcc bug report:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68485#add_comment
Thanks for having done the extra research and following up with the gcc
developers!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-02-15 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 22:42 [Buildroot] [PATCH] package/libgeos: fix build failure due to Gcc Bug 68485 Giulio Benetti
2021-02-13 21:51 ` Thomas Petazzoni
2021-02-14 23:46 ` Giulio Benetti
2021-02-15 8:58 ` Thomas Petazzoni [this message]
2021-02-15 19:27 ` Giulio Benetti
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=20210215095828.5584167d@windsurf.home \
--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