From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Francois Dugast <francois.dugast.foss@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] configs/visionfive2: fix build by adding kernel header version
Date: Mon, 8 Jul 2024 22:24:22 +0200 [thread overview]
Message-ID: <20240708222422.46a5ffa2@windsurf> (raw)
In-Reply-To: <20240706110642.939667-1-ju.o@free.fr>
On Sat, 6 Jul 2024 13:06:42 +0200
Julien Olivain <ju.o@free.fr> wrote:
> commit d9e6d2d081 "configs/visionfive2: update kernel to upstream
> 6.8.2" removed the config directive:
>
> BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_15=y
>
> but forgot to add:
>
> BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_8=y
>
> It was most likely generated with a "make savedefconfig", while Linux
> kernel v6.8 was the default at that time. After commit aa70c331a2
> "linux: bump latest version to 6.9", the defconfig failed to build
> with error:
>
> Incorrect selection of kernel headers: expected 6.9.x, got 6.8.x
>
> This commit fixes the defconfig by adding back the kernel custom header
> version.
>
> Fixes:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/7271150175
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> configs/visionfive2_defconfig | 1 +
> 1 file changed, 1 insertion(+)
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
next prev parent reply other threads:[~2024-07-08 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 11:06 [Buildroot] [PATCH 1/1] configs/visionfive2: fix build by adding kernel header version Julien Olivain
2024-07-08 20:24 ` Thomas Petazzoni via buildroot [this message]
2024-07-11 8:17 ` 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=20240708222422.46a5ffa2@windsurf \
--to=buildroot@buildroot.org \
--cc=francois.dugast.foss@gmail.com \
--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