All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
	buildroot@buildroot.org, "Markus Mayer" <mmayer@broadcom.com>
Cc: Jugurtha BELKALEM <jugurtha.belkalem@smile.fr>,
	Alexander Egorenkov <egorenar-dev@posteo.net>,
	Bernd Kuhls <bernd@kuhls.net>, Julien Olivain <ju.o@free.fr>,
	Laurent Vivier <laurent@vivier.eu>,
	"Wojciech M. Zabolotny" <wzab01@gmail.com>,
	Francis Laniel <flaniel@linux.microsoft.com>,
	James Hilliard <james.hilliard1@gmail.com>,
	Romain Naour <romain.naour@gmail.com>,
	Qais Yousef <qais.yousef@arm.com>
Subject: Re: [Buildroot] [PATCH v3] package/elfutils: ensure we have 5.0 kernel headers for aarch64
Date: Tue, 4 Mar 2025 05:28:02 -0800	[thread overview]
Message-ID: <0c66ba0f-9efa-4cc0-8a36-71b54e25979e@gmail.com> (raw)
In-Reply-To: <20250303155310.513886-1-alex.bennee@linaro.org>



On 03/03/2025 07:53, Alex Bennée wrote:
> Since Buildroot commit [1] "package/elfutils: bump to version 0.192"
> elfutils fails to build on Aarch64 with toolchain including Kernel older
> than version 5.0. Error shows:
> 
>      aarch64_initreg.c: In function 'aarch64_set_initial_registers_tid':
>      aarch64_initreg.c:61:24: error: storage size of 'pac_mask' isn't
>      known
>         61 |   struct user_pac_mask pac_mask;
>            |                        ^~~~~~~~
> 
> elfutils 0.192 introduced a Aarch64 pointer authentication support in
> upstream commit [2].
> 
> For reference, the user_pac_mask structure was introduced in Kernel
> upstream commit [3], included in Kernel v5.0.
> 
> Fixes:
> - e.g https://autobuild.buildroot.org/results/5156901a73be52ce8ffbf10729e6852499a300be/
> - 4/6 of the failures here: https://autobuild.buildroot.org/?reason=elfutils-0.192&arch=aarch64
> 
> [1] https://gitlab.com/buildroot.org/buildroot/-/commit/5eb734766b24de5fce6e586897cd4827f8855442
> [2] https://sourceware.org/git/?p=elfutils.git;a=commitdiff;h=64e3b451ad2cec8d45661b1816e3d2dc4431f3ca
> [3] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ec6e822d1a22d0eef1d1fa260dff751dba9a4258
> 
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Message-Id: <20250217140332.310347-1-alex.bennee@linaro.org>

Was there a particular reason you decided not to take this upstream 
patch and just spun a v3:

https://sourceware.org/git/?p=elfutils.git;a=commit;h=52a747a316042e70a22acb489df9e51bfc6bf2d5

-- 
Florian

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-03-04 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 15:53 [Buildroot] [PATCH v3] package/elfutils: ensure we have 5.0 kernel headers for aarch64 Alex Bennée
2025-03-04 13:28 ` Florian Fainelli [this message]
2025-03-04 14:30   ` Alex Bennée
2025-03-04 22:58     ` Markus Mayer 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=0c66ba0f-9efa-4cc0-8a36-71b54e25979e@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=bernd@kuhls.net \
    --cc=buildroot@buildroot.org \
    --cc=egorenar-dev@posteo.net \
    --cc=flaniel@linux.microsoft.com \
    --cc=james.hilliard1@gmail.com \
    --cc=ju.o@free.fr \
    --cc=jugurtha.belkalem@smile.fr \
    --cc=laurent@vivier.eu \
    --cc=mmayer@broadcom.com \
    --cc=qais.yousef@arm.com \
    --cc=romain.naour@gmail.com \
    --cc=wzab01@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 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.