From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Quentin Monnet <qmo@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
James Clark <james.clark@linaro.org>,
Ian Rogers <irogers@google.com>
Subject: Re: [PATCH 2/2] tools build feature: Don't set feature-libcap=1 if libcap-devel isn't available
Date: Thu, 12 Dec 2024 15:32:23 -0300 [thread overview]
Message-ID: <Z1ssN_Ktym-1tvZ6@x1> (raw)
In-Reply-To: <c63063b3-b2cc-43af-b026-98c992e9bbf3@kernel.org>
On Thu, Dec 12, 2024 at 10:16:38AM +0000, Quentin Monnet wrote:
> 2024-12-11 20:25 UTC-0800 ~ Ian Rogers <irogers@google.com>
> > On Wed, Dec 11, 2024 at 2:45 PM Arnaldo Carvalho de Melo
> > <acme@kernel.org> wrote:
> >>
> >> From: Arnaldo Carvalho de Melo <acme@redhat.com>
> >>
> >> libcap isn't tested in the tools/build/feature/test-all.c fast path
> >> feature detection process, so don't set it as available if test-all
> >> manages to build.
> >>
> >> There are other users of this feature detection mechanism, and they
> >> explicitely ask for libcap to be tested, so are not affected by this
> >> patch, for instance, with this patch in place:
> >>
> >> $ make -C tools/bpf/bpftool/ clean
> >> <SNIP>
> >> make: Leaving directory '/home/acme/git/perf-tools-next/tools/bpf/bpftool'
> >> ⬢ [acme@toolbox perf-tools-next]$ make -C tools/bpf/bpftool/
> >> make: Entering directory '/home/acme/git/perf-tools-next/tools/bpf/bpftool'
> >>
> >> Auto-detecting system features:
> >> ... clang-bpf-co-re: [ on ]
> >> ... llvm: [ on ]
> >> ... libcap: [ on ]
> >> ... libbfd: [ on ]
> >> ... libelf-zstd: [ on ]
> >> <SNIP>
> >> LINK bpftool
> >> make: Leaving directory '/home/acme/git/perf-tools-next/tools/bpf/bpftool'
> >> $
> >> $ sudo rpm -e libcap-devel
> >> $ make -C tools/bpf/bpftool/
> >> <SNIP>
> >> make: Entering directory '/home/acme/git/perf-tools-next/tools/bpf/bpftool'
> >>
> >> Auto-detecting system features:
> >> ... clang-bpf-co-re: [ on ]
> >> ... llvm: [ on ]
> >> ... libcap: [ OFF ]
> >> ... libbfd: [ on ]
> >> ... libelf-zstd: [ on ]
> >>
> >> $
> >>
> >> Cc: Adrian Hunter <adrian.hunter@intel.com>
> >> Cc: Ian Rogers <irogers@google.com>
> >> Cc: James Clark <james.clark@linaro.org>
> >> Cc: Jiri Olsa <jolsa@kernel.org>
> >> Cc: Kan Liang <kan.liang@linux.intel.com>
> >> Cc: Namhyung Kim <namhyung@kernel.org>
> >> Cc: Quentin Monnet <qmo@kernel.org>
> >> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> >
> > Reviewed-by: Ian Rogers <irogers@google.com>
>
>
> Acked-by: Quentin Monnet <qmo@kernel.org>
>
> Thanks Arnaldo for checking the bpftool build :)
Thanks! Added to the cset.
- Arnaldo
prev parent reply other threads:[~2024-12-12 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 22:45 [PATCH 0/2] Fast path feature detection fixes Arnaldo Carvalho de Melo
2024-12-11 22:45 ` [PATCH 1/2] tools build feature: Add some comments to explain the FEATURE_TESTS logic Arnaldo Carvalho de Melo
2024-12-12 4:24 ` Ian Rogers
2024-12-11 22:45 ` [PATCH 2/2] tools build feature: Don't set feature-libcap=1 if libcap-devel isn't available Arnaldo Carvalho de Melo
2024-12-12 4:25 ` Ian Rogers
2024-12-12 10:16 ` Quentin Monnet
2024-12-12 18:32 ` Arnaldo Carvalho de Melo [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=Z1ssN_Ktym-1tvZ6@x1 \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=qmo@kernel.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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