From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
Cc: Ben Hutchings <ben.hutchings@mind.be>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH] package/zlib-ng: Add upstream patch to fix build with uclibc
Date: Thu, 11 Aug 2022 21:29:50 +0200 [thread overview]
Message-ID: <8735e2k28h.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220722230033.673ee11e@windsurf> (Thomas Petazzoni via buildroot's message of "Fri, 22 Jul 2022 23:00:33 +0200")
>>>>> "Thomas" == Thomas Petazzoni via buildroot <buildroot@buildroot.org> writes:
> On Tue, 14 Jun 2022 17:18:57 +0200
> Ben Hutchings <ben.hutchings@mind.be> wrote:
>> Fix the following build failure with uclibc on arm architectures (and
>> similar on powerpc):
>>
>> /home/buildroot/autobuild/instance-2/output-1/build/zlib-ng-2.0.6/arch/arm/armfeature.c:4:12: fatal error: sys/auxv.h: No such file or directory
>> 4 | # include <sys/auxv.h>
>> | ^~~~~~~~~~~~
>> compilation terminated.
>>
>> Signed-off-by: Ben Hutchings <ben.hutchings@mind.be>
>> ---
>> ...-sys-auxv.h-exists-at-configure-time.patch | 90 +++++++++++++++++++
>> 1 file changed, 90 insertions(+)
>> create mode 100644 package/zlib-ng/0003-zlib-ng-check-that-sys-auxv.h-exists-at-configure-time.patch
> Applied to master after adding a reference to an autobuilder failure
> that this is fixing.
Committed to 2022.05.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-08-11 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 15:18 [Buildroot] [PATCH] package/zlib-ng: Add upstream patch to fix build with uclibc Ben Hutchings
2022-07-22 21:00 ` Thomas Petazzoni via buildroot
2022-08-11 19:29 ` Peter Korsgaard [this message]
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=8735e2k28h.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=ben.hutchings@mind.be \
--cc=buildroot@buildroot.org \
--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