From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/util-linux: fix build with uclibc-ng < 1.0.39
Date: Fri, 12 Jul 2024 12:55:37 +0200 [thread overview]
Message-ID: <20240712125537.34a68c69@windsurf> (raw)
In-Reply-To: <20240523170523.1492521-1-fontaine.fabrice@gmail.com>
On Thu, 23 May 2024 19:05:23 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Fix the following build failure with uclibc-ng < 1.0.39 (i.e., without
> https://github.com/wbx-github/uclibc-ng/commit/85ac4f04d94e98389a8315e720630d0f95bfdfd6)
> raised since bump to version 2.39 in commit
> ad276d94a392fb13244e042851a44269e6254d61 and
> https://github.com/util-linux/util-linux/commit/03a254f010b08da1175f50a8ae7882e59228f1b4:
>
> sys-utils/setarch.c:106:7: error: 'PER_LINUX32_3GB' undeclared here (not in a function); did you mean 'PER_LINUX32'?
> 106 | X(PER_LINUX32_3GB) \
> | ^~~~~~~~~~~~~~~
>
> Fixes: ad276d94a392fb13244e042851a44269e6254d61
> - http://autobuild.buildroot.org/results/fb1feb47f2660882fa53f66bacc63e191fd52175
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...ch.c-fix-build-with-uclibc-ng-1.0.39.patch | 39 +++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100644 package/util-linux/0001-sys-utils-setarch.c-fix-build-with-uclibc-ng-1.0.39.patch
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-12 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 17:05 [Buildroot] [PATCH 1/1] package/util-linux: fix build with uclibc-ng < 1.0.39 Fabrice Fontaine
2024-07-12 10:55 ` Thomas Petazzoni via buildroot [this message]
2024-07-28 10:51 ` 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=20240712125537.34a68c69@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--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