From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935644AbeAHRL3 (ORCPT + 1 other); Mon, 8 Jan 2018 12:11:29 -0500 Received: from mx1.redhat.com ([209.132.183.28]:39664 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932354AbeAHRL0 (ORCPT ); Mon, 8 Jan 2018 12:11:26 -0500 Date: Mon, 8 Jan 2018 18:11:22 +0100 From: Jiri Olsa To: Arnaldo Carvalho de Melo Cc: Jiri Olsa , Peter Zijlstra , lkml , Ingo Molnar , Namhyung Kim , David Ahern , Andi Kleen , Alexander Shishkin Subject: Re: [PATCH 01/12] perf tools: Enable LIBBABELTRACE by default Message-ID: <20180108171122.GC18380@krava> References: <20180107160356.28203-1-jolsa@kernel.org> <20180107160356.28203-2-jolsa@kernel.org> <20180108151709.GI25476@kernel.org> <20180108152037.GJ25476@kernel.org> <20180108152433.GK25476@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180108152433.GK25476@kernel.org> User-Agent: Mutt/1.9.1 (2017-09-22) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Mon, 08 Jan 2018 17:11:26 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Mon, Jan 08, 2018 at 12:24:33PM -0300, Arnaldo Carvalho de Melo wrote: SNIP > > Works: > > [acme@jouet perf]$ ldd ~/bin/perf | grep babel > libbabeltrace-ctf.so.1 => /lib64/libbabeltrace-ctf.so.1 (0x00007fcb688d0000) > libbabeltrace.so.1 => /lib64/libbabeltrace.so.1 (0x00007fcb67e92000) > [acme@jouet perf]$ rpm -q libbabeltrace-devel > libbabeltrace-devel-1.5.3-1.fc27.x86_64 > [acme@jouet perf]$ > > But then, if we show: > > Auto-detecting system features: > ... dwarf: [ on ] > ... dwarf_getlocations: [ on ] > ... glibc: [ on ] > ... gtk2: [ on ] > ... libaudit: [ on ] > ... 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 ] > > Shoudln't we tell the user that babeltrace was linked too? the logic is just to simply display the state of features which we provide in FEATURE_DISPLAY variable, which is believed to be common and important enough to display status about maybe we could display it with 'make VF=1' output? jirka