From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Romain Naour <romain.naour@gmail.com>
Cc: Sebastian Weyer <sebastian.weyer@smile.fr>,
Jan-Benedict Glaw <jbglaw@lug-owl.de>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4] configs/qemu: update defconfigs to Linux 6.1.26
Date: Sun, 21 May 2023 22:11:34 +0200 [thread overview]
Message-ID: <20230521201134.GD621937@scaer> (raw)
In-Reply-To: <20230428224051.259264-1-romain.naour@gmail.com>
Sebastian, Romain, All,
+Jan-Benedict for BZ #15581
On 2023-04-29 00:40 +0200, Romain Naour spake thusly:
> From: Sebastian Weyer <sebastian.weyer@smile.fr>
>
> Just updating all qemu defconfigs to the latest Kernel LTS version
> including first gcc 13.1 fixes [1]
[--SNIP--]
> configs/qemu_ppc_mpc8544ds_defconfig | 4 ++--
[--SNIP--]
> diff --git a/configs/qemu_ppc_mpc8544ds_defconfig b/configs/qemu_ppc_mpc8544ds_defconfig
> index b9a0812d52..ca1a429167 100644
> --- a/configs/qemu_ppc_mpc8544ds_defconfig
> +++ b/configs/qemu_ppc_mpc8544ds_defconfig
> @@ -15,12 +15,12 @@ BR2_ROOTFS_POST_IMAGE_SCRIPT="board/qemu/post-image.sh"
> BR2_ROOTFS_POST_SCRIPT_ARGS="$(BR2_DEFCONFIG)"
>
> # Linux headers same as kernel
> -BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_17=y
> +BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_1=y
>
> # Kernel
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="5.17.7"
> +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.1.26"
> BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/qemu/ppc-mpc8544ds/linux.config"
> BR2_LINUX_KERNEL_VMLINUX=y
Did you actualy test this change? It fails to even patch the kernel:
$ make distclean
$ make qemu_ppc_mpc8544ds_defconfig
$ make linux-patch
>>> linux 6.1.26 Patching
Applying 0001-powerpc-Fix-mcpu-options-for-SPE-only-compiler.patch using patch:
patching file arch/powerpc/Makefile
Hunk #1 succeeded at 10 (offset -2 lines).
Hunk #2 FAILED at 164.
Hunk #3 succeeded at 174 with fuzz 2 (offset -1 lines).
1 out of 3 hunks FAILED -- saving rejects to file arch/powerpc/Makefile.rej
make[1]: *** [package/pkg-generic.mk:251: ...../build/linux-6.1.26/.stamp_patched] Error 1
make: *** [Makefile:23: _all] Error 2
Ditto for linux-headers, of course...
See:
https://bugs.busybox.net/show_bug.cgi?id=15581
Could you re-check on your side, and also verify the other defconfig
files, please?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-05-21 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 22:40 [Buildroot] [PATCH v4] configs/qemu: update defconfigs to Linux 6.1.26 Romain Naour
2023-05-08 20:13 ` Yann E. MORIN
2023-05-21 20:11 ` Yann E. MORIN [this message]
2023-05-24 9:28 ` Romain Naour
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=20230521201134.GD621937@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=jbglaw@lug-owl.de \
--cc=romain.naour@gmail.com \
--cc=sebastian.weyer@smile.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