From: "Gero Schwäricke" <gero.schwaericke@posteo.de>
To: buildroot@buildroot.org
Cc: "Francois Dugast" <francois.dugast.foss@gmail.com>,
"Gero Schwäricke" <gero.schwaericke@posteo.de>
Subject: [Buildroot] [PATCH] configs/sipeed_licheepi_nano_defconfig: fix missing linux headers
Date: Tue, 2 Apr 2024 21:08:52 +0000 [thread overview]
Message-ID: <20240402210856.67418-1-gero.schwaericke@posteo.de> (raw)
The build failed with:
Incorrect selection of kernel headers: expected 6.8.x, got 6.5.x
Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/6498278078
Signed-off-by: Gero Schwäricke <gero.schwaericke@posteo.de>
---
configs/sipeed_licheepi_nano_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/configs/sipeed_licheepi_nano_defconfig b/configs/sipeed_licheepi_nano_defconfig
index 8be26165d9..6eb4a3069d 100644
--- a/configs/sipeed_licheepi_nano_defconfig
+++ b/configs/sipeed_licheepi_nano_defconfig
@@ -9,6 +9,9 @@ BR2_TARGET_GENERIC_GETTY_BAUDRATE_115200=y
BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/sipeed/licheepi_nano/genimage.cfg"
+# Linux headers same as kernel
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_5=y
+
# Kernel
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
--
2.43.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-04-02 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 21:08 Gero Schwäricke [this message]
2024-04-30 22:14 ` [Buildroot] [PATCH] configs/sipeed_licheepi_nano_defconfig: fix missing linux headers Romain Naour
2024-05-15 14:44 ` 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=20240402210856.67418-1-gero.schwaericke@posteo.de \
--to=gero.schwaericke@posteo.de \
--cc=buildroot@buildroot.org \
--cc=francois.dugast.foss@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).