public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: "Vincent Stehlé" <vincent.stehle@arm.com>
Cc: buildroot@buildroot.org,
	Alistair Francis <alistair@alistair23.me>,
	Dowan Gullient <dowan.gullient@smile.fr>
Subject: Re: [Buildroot] [PATCH] package/xen: fix armv7 build with gcc-15
Date: Wed, 18 Mar 2026 19:09:33 +0100	[thread overview]
Message-ID: <9444a675ade792e71ac0afa29b1f9895@free.fr> (raw)
In-Reply-To: <20260318123714.2494747-1-vincent.stehle@arm.com>

On 18/03/2026 13:37, Vincent Stehlé wrote:
> Backport a patch from Xen 4.21 to fix the following build errors for 
> Arm v7
> with gcc-15:
> 
>   xen-4.14.6/xen/include/asm/platforms/midway.h:1: error: header guard 
> '__ASM_ARM_PLATFORMS_MIDWAY_H' followed by '#define' of a different 
> macro [-Werror=header-guard]
>   xen-4.14.6/xen/include/asm/platforms/omap5.h:1: error: header guard 
> '__ASM_ARM_PLATFORMS_OMAP5_H' followed by '#define' of a different 
> macro [-Werror=header-guard]
> 
> Since the external 32b arm toolchain has been updated to a version 
> based on
> gcc-15, the tests.package.test_xen.TestXenArmv7 python test does not 
> build
> anymore.
> Adding the patch repairs it.
> 
> Link: https://gitlab.com/buildroot.org/buildroot/-/jobs/13518318473
> Fixes: 86d453a7dc08 
> ("toolchain/toolchain-external/toolchain-external-arm-arm: bump to 
> 15.2.rel1")
> Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>
> Cc: Alistair Francis <alistair@alistair23.me>
> Cc: Dowan Gullient <dowan.gullient@smile.fr>

Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2026-03-18 18:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-18 12:37 [Buildroot] [PATCH] package/xen: fix armv7 build with gcc-15 Vincent Stehlé
2026-03-18 18:09 ` Julien Olivain via buildroot [this message]
2026-03-27 10:03 ` Thomas Perale 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=9444a675ade792e71ac0afa29b1f9895@free.fr \
    --to=buildroot@buildroot.org \
    --cc=alistair@alistair23.me \
    --cc=dowan.gullient@smile.fr \
    --cc=ju.o@free.fr \
    --cc=vincent.stehle@arm.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