From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] [autobuild.buildroot.net] Daily results for 2023-07-29
Date: Sun, 30 Jul 2023 22:58:14 +0200 [thread overview]
Message-ID: <20230730225814.108f5fcf@windsurf> (raw)
In-Reply-To: <pan$23df6$8f2c97e9$80972a17$d2124f06@ID-313208.user.individual.net>
On Sun, 30 Jul 2023 22:25:19 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Am Sun, 30 Jul 2023 05:43:11 -0000 schrieb Thomas Petazzoni via buildroot:
>
> > http://autobuild.buildroot.net/results/
> d377efffbe2112f7bdf73bbee55e655ce1e03d44
> > | s390x | host-ccache-4.8.2 | NOK |
> > http://autobuild.buildroot.net/results/
> a49c1eac4ba5ec6de71bd2dcbd201183cd28aa8d
> > | ORPH
> > or1k | host-ccache-4.8.2 | NOK |
> > http://autobuild.buildroot.net/results/
> d84de4df9e4186ee2ac6c0903fd44a53e7916fb3
> > | ORPH
>
> these build errors are caused by an ICE in host gcc, in our case
> gcc-12.3.1 on br-autobuild-1:
>
> According to https://bugs.gentoo.org/906310#c3 the error was fixed
> upstream: https://gcc.gnu.org/git/gitweb.cgi?
> p=gcc.git;h=396a4e76afec30d2461638f569cae18955eb4ad2
>
> Is it possible to update the toolchain on br-autobuild-1?
br-autobuild-1 is currently using Fedora 37, and we are up-to-date with
Fedora 37. It has the following version of gcc:
gcc version 12.3.1 20230508 (Red Hat 12.3.1-1) (GCC)
Problem is that commit 396a4e76afec30d2461638f569cae18955eb4ad2 is part
the 12.3.0 tag, and there is no gcc release that contains this commit,
which is probably why Fedora didn't pick it up.
GCC bug is at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109241.
Apparently, it will be fixed in GCC 12.4.0. No idea when 12.4.0 is
planned though :-/
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-30 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230730054316.D9D0E400FE__49774.3708708853$1690695823$gmane$org@smtp2.osuosl.org>
2023-07-30 20:25 ` [Buildroot] [autobuild.buildroot.net] Daily results for 2023-07-29 Bernd Kuhls
2023-07-30 20:58 ` Thomas Petazzoni via buildroot [this message]
2023-08-01 22:01 ` Bernd Kuhls
2023-07-30 5:43 Thomas Petazzoni via buildroot
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=20230730225814.108f5fcf@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=buildroot@uclibc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox