From: Julien Olivain <ju.o@free.fr>
To: Michael Nosthoff <buildroot@heine.tech>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/procps-ng: fix build with missing pidfd_open
Date: Tue, 25 Feb 2025 20:59:53 +0100 [thread overview]
Message-ID: <d21700582ae53ed1b3a19b54c86a4932@free.fr> (raw)
In-Reply-To: <20250225155040.3209582-2-buildroot@heine.tech>
On 25/02/2025 16:50, Michael Nosthoff via buildroot wrote:
> port back patch introduced shortly after the 4.0.5 release.
>
> Fixes:
> checking for __NR_pidfd_open... no
> configure: error: Neither pidfd_open or __NR_pidfd_open found.
> Disable pidwait with configure option --disable-pidwait
>
> happening with this defconfig:
>
> BR2_arm=y
> BR2_cortex_a15_a7=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_INIT_SYSTEMD=y
> BR2_PACKAGE_PROCPS_NG=y
>
> Signed-off-by: Michael Nosthoff <buildroot@heine.tech>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-02-25 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 15:50 [Buildroot] [PATCH] package/procps-ng: fix build with missing pidfd_open Michael Nosthoff via buildroot
2025-02-25 19:59 ` Julien Olivain [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=d21700582ae53ed1b3a19b54c86a4932@free.fr \
--to=ju.o@free.fr \
--cc=buildroot@buildroot.org \
--cc=buildroot@heine.tech \
/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