[Buildroot] [PATCH 1/1] support/testing: test_dpdk: fix test after bootlin toolchains update

[Buildroot] [PATCH 1/1] support/testing: test_dpdk: fix test after bootlin toolchains update

[Julien Olivain via buildroot]

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.

Fixes:
https://gitlab.com/buildroot.org/buildroot/-/jobs/10984686010

[1] https://gitlab.com/buildroot.org/buildroot/-/commit/947dbc92a20c5acea7882166cae7893e6ea661e1

Signed-off-by: Julien Olivain <ju.o@free.fr>
---
 support/testing/tests/package/test_dpdk.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/support/testing/tests/package/test_dpdk.py b/support/testing/tests/package/test_dpdk.py
index de2828298a..6f55cddee8 100644
--- a/support/testing/tests/package/test_dpdk.py
+++ b/support/testing/tests/package/test_dpdk.py
@@ -11,7 +11,7 @@ class TestDPDK(infra.basetest.BRTest):
         BR2_TOOLCHAIN_EXTERNAL=y
         BR2_LINUX_KERNEL=y
         BR2_LINUX_KERNEL_CUSTOM_VERSION=y
-        BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.6.58"
+        BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.6.102"
         BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
         BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/x86_64/linux.config"
         BR2_LINUX_KERNEL_NEEDS_HOST_LIBELF=y
-- 
2.50.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] support/testing: test_dpdk: fix test after bootlin toolchains update

[Thomas Petazzoni via buildroot]

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

Re: [Buildroot] [PATCH 1/1] support/testing: test_dpdk: fix test after bootlin toolchains update

[Thomas Petazzoni via buildroot]

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.
> 
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/10984686010
> 
> [1] https://gitlab.com/buildroot.org/buildroot/-/commit/947dbc92a20c5acea7882166cae7893e6ea661e1
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
>  support/testing/tests/package/test_dpdk.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] support/testing: test_dpdk: fix test after bootlin toolchains update

[Julien Olivain via buildroot]

Hi Thomas,

On 16/08/2025 11:05, Thomas Petazzoni via buildroot wrote:
> 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?

I believe the Bootlin toolchain variants were just sorted
alphabetically. So the order end up to be:

- glibc bleeding-edge
- glibc stable
- musl bleeding-edge
- musl stable
- uclibc bleeding-edge
- uclibc stable

This is also why we need to specify
BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_xyz_GLIBC_STABLE=y
when switching a defconfig to use the bootlin stable toolchain.
See for example:
https://gitlab.com/buildroot.org/buildroot/-/commit/47f4e3810c981e8cee19d8a411b38c771ebd2381

Having glibc in first position makes sense, since Buildroot switched
to that libc by default a while back.

As you mentioned, it would probably make sense to invert the order of
bleeding-edge and stable to have the stable by default (or to add a
"default y"). Doing so will probably require to refresh all the
defconfigs with "make savedefconfig".

The same ordering question could be raised for the general
external toolchain type. We always had some variability in toolchain
when selecting an external toolchain depending on the target cpu
architecture. For example for the BR2_aarch64 architecture, selecting
BR2_TOOLCHAIN_EXTERNAL=y then defaults to
"Arm AArch64 14.2.rel1", then propose "Linaro AArch64 2018.05", and then
"Bootlin toolchains" (this time, not in alphabetical order).

I think this is the reason why you were not expecting a Bootlin
bleeding-edge, because in for Aarch64, we end up to
"Arm AArch64 14.2.rel1" and many of our tests using an external
toolchain are Aarch64. Only few are using x86_64. Note that
all the tests I fixed were x86_64.

Maybe this is a question that could be discussed during the upcoming
Buildroot DevDays.

Since the Bootlin toolchains are supporting most cpu architectures,
we could have the stable variant as default for all supported
architectures by default.

What do you think?

Best regards,

Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

Re: [Buildroot] [PATCH 1/1] support/testing: test_dpdk: fix test after bootlin toolchains update

[Thomas Perale via buildroot]

In reply of:
> 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.
> 
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/10984686010
> 
> [1] https://gitlab.com/buildroot.org/buildroot/-/commit/947dbc92a20c5acea7882166cae7893e6ea661e1
> 
> Signed-off-by: Julien Olivain <ju.o@free.fr>

Applied to 2025.02.x & 2025.05.x. Thanks

> ---
>  support/testing/tests/package/test_dpdk.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/support/testing/tests/package/test_dpdk.py b/support/testing/tests/package/test_dpdk.py
> index de2828298a..6f55cddee8 100644
> --- a/support/testing/tests/package/test_dpdk.py
> +++ b/support/testing/tests/package/test_dpdk.py
> @@ -11,7 +11,7 @@ class TestDPDK(infra.basetest.BRTest):
>          BR2_TOOLCHAIN_EXTERNAL=y
>          BR2_LINUX_KERNEL=y
>          BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> -        BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.6.58"
> +        BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.6.102"
>          BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
>          BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/x86_64/linux.config"
>          BR2_LINUX_KERNEL_NEEDS_HOST_LIBELF=y
> -- 
> 2.50.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot