From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
Linux-kernel@vger.kernel.org, ak@linux.intel.com,
kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v2 3/4] perf version: Print the compiled-in status of libraries
Date: Wed, 28 Mar 2018 21:57:43 +0800 [thread overview]
Message-ID: <4375e4ec-dba9-a442-25f1-ae8f706d52c9@linux.intel.com> (raw)
In-Reply-To: <20180328131053.GL3102@krava>
On 3/28/2018 9:10 PM, Jiri Olsa wrote:
> On Wed, Mar 28, 2018 at 10:57:07PM +0800, Jin Yao wrote:
>
> SNIP
>
>> +
>> +static void library_status(void)
>> +{
>> + STATUS(HAVE_DWARF_SUPPORT, dwarf);
>> + STATUS(HAVE_DWARF_GETLOCATIONS, dwarf_getlocations);
>> + STATUS(HAVE_GLIBC_SUPPORT, glibc);
>> + STATUS(HAVE_GTK2_SUPPORT, gtk2);
>> + STATUS(HAVE_LIBAUDIT_SUPPORT, libaudit);
>> + STATUS(HAVE_LIBBFD_SUPPORT, libbfd);
>> + STATUS(HAVE_LIBELF_SUPPORT, libelf);
>> + STATUS(HAVE_LIBNUMA_SUPPORT, libnuma);
>> + STATUS(HAVE_LIBNUMA_SUPPORT, numa_num_possible_cpus);
>> + STATUS(HAVE_LIBPERL_SUPPORT, libperl);
>> + STATUS(HAVE_LIBPYTHON_SUPPORT, libpython);
>> + STATUS(HAVE_SLANG_SUPPORT, libslang);
>> + STATUS(HAVE_LIBCRYPTO_SUPPORT, libcrypto);
>> + STATUS(HAVE_LIBUNWIND_SUPPORT, libunwind);
>> + STATUS(HAVE_DWARF_SUPPORT, libdw-dwarf-unwind);
>> + STATUS(HAVE_ZLIB_SUPPORT, zlib);
>> + STATUS(HAVE_LZMA_SUPPORT, lzma);
>> + STATUS(HAVE_AUXTRACE_SUPPORT, get_cpuid);
>> + STATUS(HAVE_LIBBPF_SUPPORT, bpf);
>> +
>> + on_off_print("on");
>> + printf(": library is compiled-in\n");
>> +
>> + on_off_print("OFF");
>> + printf(": library is disabled in make configuration\n");
>> + printf(" OR library is not installed in build environment\n");
>
> [jolsa@krava perf]$ ./perf -vv
> perf version 4.16.rc6.gcc183d
> dwarf: [ on ]
> dwarf_getlocations: [ on ]
> glibc: [ on ]
> gtk2: [ on ]
> libaudit: [ OFF ]
> libbfd: [ on ]
> libelf: [ on ]
> libnuma: [ on ]
> numa_num_possible_cpus: [ on ]
> libperl: [ on ]
> libpython: [ on ]
> libslang: [ on ]
> libcrypto: [ on ]
> libunwind: [ on ]
> libdw-dwarf-unwind: [ on ]
> zlib: [ on ]
> lzma: [ on ]
> get_cpuid: [ on ]
> bpf: [ on ]
> [ on ]: library is compiled-in
> [ OFF ]: library is disabled in make configuration
> OR library is not installed in build environment
>
> did anyone asked for this ^^^ help messages? I don't think they are necessary
>
> jirka
>
No one ask for this. Since it's not very necessary, I will remove this
message.
Thanks
Jin Yao
next prev parent reply other threads:[~2018-03-28 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 14:57 [PATCH v2 0/4] Support perf -vv Jin Yao
2018-03-28 14:57 ` [PATCH v2 1/4] tools include: Add config.h header file Jin Yao
2018-03-28 14:57 ` [PATCH v2 3/4] perf version: Print the compiled-in status of libraries Jin Yao
2018-03-28 13:10 ` Jiri Olsa
2018-03-28 13:57 ` Jin, Yao [this message]
2018-03-28 14:57 ` [PATCH v2 4/4] perf: Support perf -vv Jin Yao
2018-03-28 13:22 ` Jiri Olsa
2018-03-28 14:00 ` Jin, Yao
2018-03-28 14:19 ` Jiri Olsa
2018-03-28 14:56 ` Jin, Yao
2018-03-28 15:46 ` Ingo Molnar
2018-03-29 0:52 ` Jin, Yao
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=4375e4ec-dba9-a442-25f1-ae8f706d52c9@linux.intel.com \
--to=yao.jin@linux.intel.com \
--cc=Linux-kernel@vger.kernel.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yao.jin@intel.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).