From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Wang Nan <wangnan0@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: feature detection versus feature selection
Date: Sun, 14 Aug 2016 13:04:03 +0200 [thread overview]
Message-ID: <20160814110403.GC19532@krava> (raw)
In-Reply-To: <20160812161500.GL27651@kernel.org>
On Fri, Aug 12, 2016 at 01:15:00PM -0300, Arnaldo Carvalho de Melo wrote:
> Hey guys,
>
> Now we have this output when building tools with the feature
> detection mechanisms in tools/build/:
>
> Auto-detecting system features:
> ... dwarf: [ on ]
> ... dwarf_getlocations: [ OFF ]
> ... glibc: [ on ]
> ... gtk2: [ on ]
> ... libaudit: [ on ]
> ... libbfd: [ on ]
> ... libelf: [ on ]
> ... libnuma: [ on ]
> ... numa_num_possible_cpus: [ OFF ]
> ... libperl: [ on ]
> ... libpython: [ on ]
> ... libslang: [ on ]
> ... libcrypto: [ on ]
> ... libunwind: [ on ]
> ... libdw-dwarf-unwind: [ OFF ]
> ... zlib: [ on ]
> ... lzma: [ on ]
> ... get_cpuid: [ on ]
> ... bpf: [ on ]
>
>
> What I miss is a way to have another column that would state if
> the user had used, say, NO_LIBELF to disable libelf...
>
> Jiri, is there already some file where we have the list of
> manually disabled features? Or do you have something like that in mind?
> .config files?
my mind is empty ;-)
we could add map for that, or we could just add:
... libbfd: [ on ]
... libelf: [ OFF NO_LIBELF ]
... libnuma: [ on ]
... numa_num_possible_cpus: [ OFF ]
jirka
prev parent reply other threads:[~2016-08-14 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 16:15 feature detection versus feature selection Arnaldo Carvalho de Melo
2016-08-14 11:04 ` Jiri Olsa [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=20160814110403.GC19532@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangnan0@huawei.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