Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756760Ab3ILVSv (ORCPT ); Thu, 12 Sep 2013 17:18:51 -0400 Received: from mail-ee0-f50.google.com ([74.125.83.50]:52929 "EHLO mail-ee0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756510Ab3ILVSu (ORCPT ); Thu, 12 Sep 2013 17:18:50 -0400 Date: Thu, 12 Sep 2013 23:18:47 +0200 From: Ingo Molnar To: David Ahern Cc: Arnaldo Carvalho de Melo , Linus Torvalds , Linux Kernel Mailing List , Peter Zijlstra , Thomas Gleixner , Andrew Morton Subject: Re: [GIT PULL] perf fixes Message-ID: <20130912211846.GA7890@gmail.com> References: <20130912133855.GA23780@gmail.com> <20130912184341.GA11400@ghostprotocols.net> <52321CE4.1080804@gmail.com> <20130912201855.GC32644@gmail.com> <20130912203831.GD11400@ghostprotocols.net> <20130912204618.GA3262@gmail.com> <52322D81.5090708@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52322D81.5090708@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2098 Lines: 55 * David Ahern wrote: > On 9/12/13 1:46 PM, Ingo Molnar wrote: > >>>Mind outlining the approach you are thinking about? > >>> > >>>Firstly, please don't even think about autotools. (Just forget it exists.) > >> > >>hehe, no, that wasn't considered. > > > >/phew! :-) > > kconf approach of course: > https://lkml.org/lkml/2013/4/1/600 > (minus the manual steps in that RFC). I'm not sure what the end stage is where you'd like to arrive, but I don't think that forcing a separate configuration pass is an improvement :-/ By default a simple 'make' should build perf to the maximum extent possible, with no other input required from the user - with warnings displayed as package install suggestions. This: Enable newt-based TUI (NEWT) [N/y] (NEW) y Enable GTK-based UI (GTK2) [N/y] (NEW) n Enable support for Bionic (e.g., Android platform) (BIONIC) [N/y] (NEW) Development support for libc is available - glibc or bionic (LIBC) [N/y] (NEW) y Enable support for libelf (LIBELF) [N/y] (NEW) y Enable support for libunwind (LIBUNWIND) [N/y] (NEW) y Enable support for dwarf (DWARF) [N/y] (NEW) y Enable support for demangle (DEMANGLE) [N/y] (NEW) y Enable support for perl scripting engine (LIBPERL) [N/y] (NEW) y Enable support for python scripting engine (LIBPYTHON) [N/y] (NEW) y Enable support for libaudit (LIBAUDIT) [N/y/?] (NEW) y Enable support for libnuma (LIBNUMA) [N/y/?] (NEW) y Enable support for stack backtrace debugging (BACKTRACE) [N/y] (NEW) y would be useful only as long as each listed option is actually _buildable_. I.e. it should not be possible for the user to configure perf in a way that makes the build fail. I.e. this should go on top of a feature detection logic, allowing further customization, for features that the user might want to turn off. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/