Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Giulio Benetti <giulio.benetti@benettiengineering.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libgeos: fix build failure due to Gcc Bug 68485
Date: Mon, 15 Feb 2021 00:46:35 +0100	[thread overview]
Message-ID: <4164497f-c16c-99c9-e6e7-70e77c16c368@benettiengineering.com> (raw)
In-Reply-To: <20210213225155.6b83e879@windsurf.home>

Hi Thomas,

On 2/13/21 10:51 PM, Thomas Petazzoni wrote:
> Hello Giulio,
> 
> On Fri, 12 Feb 2021 23:42:38 +0100
> Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> 
>> Package libgeos manifests Microblaze Gcc Bug 68485 resulting in a build
>> failure due to an Internal Compiler Error.
>>
>> As done for other packages in Buildroot work around this Gcc Bug by
>> setting optimization to -O0 if BR2_TOOLCHAIN_HAS_GCC_BUG_68485=y.
>>
>> Fixes:
>> http://autobuild.buildroot.net/results/0da/0daa6b259aea5381fad86d01e6dd026b1c8ad073/
>>
>> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
>> ---
>>   package/libgeos/libgeos.mk | 8 ++++++++
>>   1 file changed, 8 insertions(+)
> 
> 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

Let's see what they answer.

Best regards
-- 
Giulio Benetti
Benetti Engineering sas

  reply	other threads:[~2021-02-14 23:46 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 [this message]
2021-02-15  8:58     ` Thomas Petazzoni
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=4164497f-c16c-99c9-e6e7-70e77c16c368@benettiengineering.com \
    --to=giulio.benetti@benettiengineering.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