From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain via buildroot <buildroot@buildroot.org>
Cc: Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] support/testing: test_dpdk: fix test after bootlin toolchains update
Date: Sat, 16 Aug 2025 11:05:33 +0200 [thread overview]
Message-ID: <20250816110533.7ec8ee44@windsurf> (raw)
In-Reply-To: <20250816001117.246947-1-ju.o@free.fr>
On Sat, 16 Aug 2025 02:11:17 +0200
Julien Olivain via buildroot <buildroot@buildroot.org> wrote:
> Since Buildroot commit [1] "update to Bootlin toolchains 2025.08-1",
> the tests.package.test_dpdk fails to build its Kernel 6.6.58 with
> gcc 15.1.0.
>
> This commit fixes the issue by updating the test Kernel version to
> the latest 6.6.y version (6.6.102 at the time of this commit) which
> includes the fix for gcc-15.
I was surprised by this, because the test only says
BR2_TOOLCHAIN_EXTERNAL=y, so I would expect the default to be a Bootlin
*stable* toolchain. But with the order in which
toolchain/toolchain-external/toolchain-external-bootlin/Config.in.options
is written, the bleeding edge toolchains are indeed the default. Is
this really a good idea? Shouldn't I change this to make the stable
toolchains be the default?
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:[~2025-08-16 9:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 0:11 [Buildroot] [PATCH 1/1] support/testing: test_dpdk: fix test after bootlin toolchains update Julien Olivain via buildroot
2025-08-16 9:05 ` Thomas Petazzoni via buildroot [this message]
2025-08-17 14:47 ` Julien Olivain via buildroot
2025-08-16 19:47 ` Thomas Petazzoni via buildroot
2025-08-21 19:21 ` Thomas Perale 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=20250816110533.7ec8ee44@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--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