From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/botan: avoid compile error with gcc 10.x
Date: Tue, 20 Aug 2024 10:58:34 +0200 [thread overview]
Message-ID: <20240820105834.01fe6286@windsurf> (raw)
In-Reply-To: <ZsO1UYTTOIY7UuJn@landeda>
Hello Waldemar, Hello Yann,
On Mon, 19 Aug 2024 23:12:49 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > Compile successfully tested with internal Buildroot toolchain for
> > sparc with gcc 12.x as gcc 11.x is not available anymore.
> >
> > The autobuild failure will be avoided now and fixed with newer external
> > bootlin toolchains.
> >
> > Fixes:
> > - http://autobuild.buildroot.org/results/ab8/ab83b920156f5a1e51ef960e4007769b5c27d0a1
> >
> > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
>
> Applied to master, thanks.
If I may chime in, one critical thing that is missing from this commit
message is since when this problem is occurring. Is it since the update
of the package in 3ba9ac62052c99d7557adf2bbad1bab0c5577a81 ? Or since
2fcc74594c457bed7f0f2a4826ada265861be6bf ?
Indeed 11a577c19e23d0b774f357b2d62ac3c41b7f201f already added a
dependency on gcc 10, so I guess it's something after that?
Again, this is important to understand if the patch needs to be
backported to LTS or not, as usual.
Thanks!
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:[~2024-08-20 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 20:53 [Buildroot] [PATCH] package/botan: avoid compile error with gcc 10.x Waldemar Brodkorb
2024-08-19 21:12 ` Yann E. MORIN
2024-08-20 8:58 ` Thomas Petazzoni via buildroot [this message]
2024-08-20 21:39 ` Yann E. MORIN
2024-09-18 11:07 ` Peter Korsgaard
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=20240820105834.01fe6286@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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