From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756871AbbCMQUs (ORCPT ); Fri, 13 Mar 2015 12:20:48 -0400 Received: from mx1.redhat.com ([209.132.183.28]:52014 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756799AbbCMQUq (ORCPT ); Fri, 13 Mar 2015 12:20:46 -0400 Date: Fri, 13 Mar 2015 17:20:11 +0100 From: Jiri Olsa To: Arnaldo Carvalho de Melo Cc: Jiri Olsa , linux-kernel@vger.kernel.org, Corey Ashford , David Ahern , Ingo Molnar , Namhyung Kim , Paul Mackerras , Peter Zijlstra Subject: Re: [PATCH 01/15] perf build: Disable default check for libbabeltrace Message-ID: <20150313162011.GA21865@krava.brq.redhat.com> References: <1426064344-21737-1-git-send-email-jolsa@kernel.org> <1426064344-21737-2-git-send-email-jolsa@kernel.org> <20150313153621.GB3467@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150313153621.GB3467@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 13, 2015 at 12:36:21PM -0300, Arnaldo Carvalho de Melo wrote: SNIP > > Auto-detecting system features: > ... dwarf: [ on ] > ... glibc: [ on ] > ... gtk2: [ on ] > ... libaudit: [ on ] > ... libbfd: [ on ] > ... libelf: [ on ] > ... libnuma: [ on ] > ... libperl: [ on ] > ... libpython: [ on ] > ... libslang: [ on ] > ... libunwind: [ OFF ] > ... libdw-dwarf-unwind: [ on ] > ... zlib: [ on ] > ... DWARF post unwind library: libdw > > GEN common-cmds.h > > It continues trying to find babeltrace, does not find it, emits the warning and > just doesn't show the OFF message :-\ > > Can you explain _why_ this is needed? I.e. is it to speed up feature checking? > In what way, etc. For casual readers the intent of this patch may be difficult > to grasp, no? > > What am I missing? this patch removes babeltrace from: - detected features display -> so user's not curious where to get the latest babeltrace version ;-) - test-all optimization -> so we could use features build speed up, missing babeltrace was stoping this but we still check for babeltrace (out of the default list code) in order to enable the ctf convert code if it's in the system I admit the extra warning about missing babeltrace support might be confusing, I can remove it.. ;-) I think we could add new class of features that are enabled just on demand and not checked by default at all, like: 'make BABELTRACE=1' or via .config, but we need to add support for that first jirka