Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755022Ab2JPPT0 (ORCPT ); Tue, 16 Oct 2012 11:19:26 -0400 Received: from mail-gh0-f174.google.com ([209.85.160.174]:57970 "EHLO mail-gh0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754938Ab2JPPTY (ORCPT ); Tue, 16 Oct 2012 11:19:24 -0400 Date: Tue, 16 Oct 2012 08:19:18 -0700 From: Arnaldo Carvalho de Melo To: Irina Tirdea Cc: Ingo Molnar , Steven Rostedt , Peter Zijlstra , LKML , Paul Mackerras , David Ahern , Namhyung Kim , Pekka Enberg , Jiri Olsa , Irina Tirdea Subject: Re: [PATCH v4 2/6] perf tools: configure shell path at compile time Message-ID: <20121016151918.GC6807@ghostprotocols.net> References: <1350344020-8071-1-git-send-email-irina.tirdea@gmail.com> <1350344020-8071-3-git-send-email-irina.tirdea@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1350344020-8071-3-git-send-email-irina.tirdea@gmail.com> X-Url: http://acmel.wordpress.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: 915 Lines: 20 Em Tue, Oct 16, 2012 at 02:33:36AM +0300, Irina Tirdea escreveu: > @@ -838,7 +840,11 @@ $(OUTPUT)builtin-help.o: builtin-help.c $(OUTPUT)common-cmds.h $(OUTPUT)PERF-CFL > $(QUIET_CC)$(CC) -o $@ -c $(ALL_CFLAGS) \ > '-DPERF_HTML_PATH="$(htmldir_SQ)"' \ > '-DPERF_MAN_PATH="$(mandir_SQ)"' \ > - '-DPERF_INFO_PATH="$(infodir_SQ)"' $< > + '-DPERF_INFO_PATH="$(infodir_SQ)"' \ > + '-DPERF_SHELL_PATH="$(PERF_SHELL_PATH)"' $< > + > +$(OUTPUT)builtin-script.o: builtin-script.c $(OUTPUT)PERF-CFLAGS > + $(QUIET_CC)$(CC) -o $@ -c $(ALL_CFLAGS) -DPERF_SHELL_PATH='"$(PERF_SHELL_PATH)"' $< Same question as for TMP, why not make it available for all files? - Arnaldo -- 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/