From: Adrian Perez de Castro <aperez@igalia.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Daily results for 2022-10-09
Date: Wed, 12 Oct 2022 16:05:46 +0300 [thread overview]
Message-ID: <20221012160546.GC2476394@igalia.com> (raw)
In-Reply-To: <20221010064610.388468291C@smtp1.osuosl.org>
[-- Attachment #1.1: Type: text/plain, Size: 850 bytes --]
Hello,
On Mon, 10 Oct 2022 06:46:03 +0000 Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> Autobuild statistics for 2022-10-09
> ===================================
>
> [...]
>
> arc | brotli-1.0.9 | NOK | http://autobuild.buildroot.net/results/a770002523411328c6933158461a007d07305c9e |
This build failure is due to an internal compiler error issue which I have
seen reported elsewhere [1], and the fix has made it into upstream GCC:
https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=9bb20299ba1d1cc3bbd83a07a777fcc5a93cfeb0
GCC 12 should be unaffected. What is the best way to fix this? Should we
disable the brotli package when GCC 11 is in use, import a backported fix
to GCC 11, or...?
Cheers,
—Adrián
---
[1] https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/issues/398
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-12 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 6:46 [Buildroot] [autobuild.buildroot.net] Daily results for 2022-10-09 Thomas Petazzoni via buildroot
2022-10-12 13:05 ` Adrian Perez de Castro [this message]
2022-10-12 13:17 ` 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=20221012160546.GC2476394@igalia.com \
--to=aperez@igalia.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.