From: Peter Korsgaard <peter@korsgaard.com>
To: Neal Frager <neal.frager@amd.com>
Cc: <buildroot@buildroot.org>, <arnout@rnout.be>,
<luca.ceresoli@bootlin.com>, <thomas.petazzoni@bootlin.com>,
<michal.simek@amd.com>, <ju.o@free.fr>,
<brandon.maier@collins.com>, <romain.naour@smile.fr>,
<romain.naour@gmail.com>, <ibai.erkiaga-elorza@amd.com>,
<yann.morin@orange.com>, <alistair@alistair23.me>,
<brian.j.wood2@boeing.com>, <matthew.l.weber3@boeing.com>,
<stefano.stabellini@amd.com>, <micheal.saleab@amd.com>,
<stewart.hildebrand@amd.com>, <john.ernberg@actia.se>
Subject: Re: [Buildroot] [PATCH v5 1/4] package/xen: fix build error when BR2_PACKAGE_XEN_TOOLS not enabled
Date: Wed, 16 Sep 2026 08:51:25 +0200 [thread overview]
Message-ID: <877bklofiq.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20260826064649.292291-1-neal.frager@amd.com> (Neal Frager's message of "Wed, 26 Aug 2026 07:46:46 +0100")
>>>>> "Neal" == Neal Frager <neal.frager@amd.com> writes:
> The 0002-Update-linker-flags.patch assumes that the qemu-xen files are included
> in the xen source tree. However, if BR2_PACKAGE_XEN_TOOLS is not enabled, the
> qemu-xen dependency will not be handled and the patch will fail to apply with
> the following error.
> Fixes: build error below
> Applying 0002-Update-linker-flags.patch using patch:
> patching file tools/Makefile
> Hunk #1 succeeded at 36 (offset -1 lines).
> Hunk #2 succeeded at 185 (offset -8 lines).
> can't find file to patch at input line 76
> Perhaps you used the wrong -p or --strip option?
> The text leading up to this was:
> --------------------------
> |diff --git a/tools/qemu-xen/include/hw/xen/xen_native.h b/tools/qemu-xen/include/hw/xen/xen_native.h
> |index 6bcc83ba..2590904e 100644
> |--- a/tools/qemu-xen/include/hw/xen/xen_native.h
> |+++ b/tools/qemu-xen/include/hw/xen/xen_native.h
> --------------------------
> No file to patch. Skipping patch.
> 1 out of 1 hunk ignored
> make: *** [package/pkg-generic.mk:239: output/build/xen-4.21.1/.stamp_patched] Error 1
> To avoid making BR2_PACKAGE_XEN_TOOLS a required option, fix the
> 0002-Update-linker-flags.patch so that modifying source from the qemu-xen
> package is no longer included.
> Instead of patching qemu-xen, a better solution is undefining the
> __XEN_INTERFACE_VERSION__ from the qemu-xen package.
> To test:
> BR2_aarch64=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN=y
> BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_AARCH64_GLIBC_STABLE=y
> BR2_PACKAGE_XEN=y
> # BR2_PACKAGE_XEN_TOOLS is not set
> Signed-off-by: Neal Frager <neal.frager@amd.com>
Committed, thanks - And sorry for the slow response!
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-09-16 6:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 6:46 [Buildroot] [PATCH v5 1/4] package/xen: fix build error when BR2_PACKAGE_XEN_TOOLS not enabled Neal Frager via buildroot
2026-08-26 6:46 ` [Buildroot] [PATCH v5 2/4] package/xen: add custom version support Neal Frager via buildroot
2026-08-27 0:45 ` Matthew Weber
2026-08-26 6:46 ` [Buildroot] [PATCH v5 3/4] package/xen: add custom tarball support Neal Frager via buildroot
2026-08-27 0:46 ` Matthew Weber
2026-08-28 10:45 ` Stewart Hildebrand via buildroot
2026-08-26 6:46 ` [Buildroot] [PATCH v5 4/4] package/xen: add custom git support Neal Frager via buildroot
2026-08-27 0:47 ` Matthew Weber
2026-08-27 0:43 ` [Buildroot] [PATCH v5 1/4] package/xen: fix build error when BR2_PACKAGE_XEN_TOOLS not enabled Matthew Weber
2026-08-28 10:36 ` Stewart Hildebrand via buildroot
2026-09-11 5:21 ` Frager, Neal via buildroot
2026-09-16 6:51 ` Peter Korsgaard [this message]
2026-09-25 14:43 ` Raphaël Mélotte 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=877bklofiq.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=alistair@alistair23.me \
--cc=arnout@rnout.be \
--cc=brandon.maier@collins.com \
--cc=brian.j.wood2@boeing.com \
--cc=buildroot@buildroot.org \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=john.ernberg@actia.se \
--cc=ju.o@free.fr \
--cc=luca.ceresoli@bootlin.com \
--cc=matthew.l.weber3@boeing.com \
--cc=michal.simek@amd.com \
--cc=micheal.saleab@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--cc=stefano.stabellini@amd.com \
--cc=stewart.hildebrand@amd.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.