buildroot.buildroot.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 26 Nov 2024 14:57:38 +0100	[thread overview]
Message-ID: <20241126145738.0b2e25cf@windsurf> (raw)
In-Reply-To: <CAFkzVZbeK3a-5ze3g9hWod5uhHqq1tbL+eMZ+Bz8nA9noMherA@mail.gmail.com>

On Tue, 26 Nov 2024 09:50:12 +0800
Scott Fan <fancp2007@gmail.com> wrote:

> Maybe it should be as follows:
> 
> ifeq ($(BR2_TOOLCHAIN_HEADERS_AT_LEAST_5_3),y)
> PROCPS_NG_CONF_OPTS += --disable-pidwait
> endif

If you write it this way, it will disable pidwait on all configurations
with headers >= 5.3. Don't you want to do exactly the opposite?

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

  reply	other threads:[~2024-11-26 13:57 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 [this message]
2024-11-27  0:35           ` Scott Fan
2024-11-27  1:01             ` Scott Fan
2024-11-27  7:44             ` Thomas Petazzoni via buildroot
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=20241126145738.0b2e25cf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).