From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Scott Fan <fancp2007@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/procps-ng: fix pidfd_open checking
Date: Wed, 27 Nov 2024 08:44:16 +0100 [thread overview]
Message-ID: <20241127084416.2467f7e0@windsurf> (raw)
In-Reply-To: <CAFkzVZbXtKAezUsDyDtYxhwg5CQ0A5tBnrmA9JPmi2OwGOXtXA@mail.gmail.com>
On Wed, 27 Nov 2024 08:35:42 +0800
Scott Fan <fancp2007@gmail.com> wrote:
> Sorry, I made a mistake, it should be:
>
> ifeq ($(BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_3),)
> PROCPS_NG_CONF_OPTS += --disable-pidwait
> endif
Correct.
> But another problem is that the --disable-pidwait option does not
> exist in the v4.0.4 version unless the following patch is applied.
> https://gitlab.com/procps-ng/procps/-/commit/2507bc475782ff5e0541d37c780dff1e293c9553
Well, we can simply backport this patch for the time being, until
there's a newer release that includes this commit.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-11-27 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 0:20 [Buildroot] [PATCH] package/procps-ng: fix pidfd_open checking Scott Fan
2024-10-31 18:18 ` Thomas Petazzoni via buildroot
2024-11-01 1:31 ` Scott Fan
2024-11-04 13:23 ` Scott Fan
2024-11-24 16:29 ` Thomas Petazzoni via buildroot
2024-11-26 1:50 ` Scott Fan
2024-11-26 13:57 ` Thomas Petazzoni via buildroot
2024-11-27 0:35 ` Scott Fan
2024-11-27 1:01 ` Scott Fan
2024-11-27 7:44 ` Thomas Petazzoni via buildroot [this message]
2024-11-28 3:50 ` Scott Fan
2024-12-05 16:57 ` Peter Korsgaard
2024-12-07 9:47 ` 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=20241127084416.2467f7e0@windsurf \
--to=buildroot@buildroot.org \
--cc=fancp2007@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 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.