From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/file: fix musl compile issue
Date: Sat, 26 Oct 2024 23:27:39 +0200 [thread overview]
Message-ID: <20241026232739.471f9dc6@windsurf> (raw)
In-Reply-To: <Zs7Q89h62j3hCq5x@waldemar-brodkorb.de>
On Wed, 28 Aug 2024 09:25:39 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> It is not totally clear which update is responsible for the
> breakage. The breakage has been occurring for as long as Jan 2022.
> Therefore it should be backported to older supported buildroot releases.
>
> Add a patch from Gentoo people, also reported Upstream to fix the
> issue.
>
> Fixes:
>
> http://autobuild.buildroot.org/results/abf/abfe66cec3680d396c5774ba492f34599e513edc/
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> v1->v2:
> - rework commit message suggested by Thomas Petazzoni
> ---
> .../0001-file-seccomp-fstatat64-musl.patch | 32 +++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 package/file/0001-file-seccomp-fstatat64-musl.patch
I am not a big fan of non-upstreamable patches, especially as the real
issue seems to come from musl itself (as acknowledged by Rich Felker).
But OK, let's move forward, so I merged this.
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
prev parent reply other threads:[~2024-10-26 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 7:25 [Buildroot] [PATCH v2] package/file: fix musl compile issue Waldemar Brodkorb
2024-10-26 21:27 ` Thomas Petazzoni via buildroot [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=20241026232739.471f9dc6@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.org \
/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