From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Any idea why "make V=1" isn't working for me? Date: Sat, 10 Oct 2015 15:23:42 +0300 Message-ID: <83h9lysyi9.fsf@gnu.org> References: <83612ft8bs.fsf@gnu.org> <83k2qvrnb1.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1444479841 9529 80.91.229.3 (10 Oct 2015 12:24:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 10 Oct 2015 12:24:01 +0000 (UTC) Cc: emacs-devel@gnu.org To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 10 14:23:53 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZktBm-0002iu-Vi for ged-emacs-devel@m.gmane.org; Sat, 10 Oct 2015 14:23:51 +0200 Original-Received: from localhost ([::1]:44739 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZktBg-0000fX-Vt for ged-emacs-devel@m.gmane.org; Sat, 10 Oct 2015 08:23:44 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45566) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZktBd-0000fI-Rz for emacs-devel@gnu.org; Sat, 10 Oct 2015 08:23:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZktBa-0003Ke-PJ for emacs-devel@gnu.org; Sat, 10 Oct 2015 08:23:41 -0400 Original-Received: from mtaout25.012.net.il ([80.179.55.181]:49859) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZktBa-0003JZ-Cw for emacs-devel@gnu.org; Sat, 10 Oct 2015 08:23:38 -0400 Original-Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0NW000M007AWYB00@mtaout25.012.net.il> for emacs-devel@gnu.org; Sat, 10 Oct 2015 15:21:03 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.94.185.246]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NW000N1O7N3AO10@mtaout25.012.net.il>; Sat, 10 Oct 2015 15:21:03 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:191133 Archived-At: > From: Juanma Barranquero > Date: Sat, 10 Oct 2015 13:32:34 +0200 > Cc: Emacs developers > > > Can you post your nt/Makefile? > > Attached. Now everything becomes clear. Here's the problem: > # 'make' verbosity. > AM_DEFAULT_VERBOSITY = 0 > > AM_V_CC = $(am__v_CC_0) > am__v_CC_ = $(am__v_CC_0) > am__v_CC_0 = @echo " CC " $@; > am__v_CC_1 = > > AM_V_CCLD = $(am__v_CCLD_0) > am__v_CCLD_ = $(am__v_CCLD_0) > am__v_CCLD_0 = @echo " CCLD " $@; > am__v_CCLD_1 = > > AM_V_RC = $(am__v_RC_0) > am__v_RC_ = $(am__v_RC_0) > am__v_RC_0 = @echo " RC " $@; > am__v_RC_1 = On my system, the same fragment is this: # 'make' verbosity. AM_DEFAULT_VERBOSITY = 0 AM_V_CC = $(am__v_CC_$(V)) am__v_CC_ = $(am__v_CC_$(AM_DEFAULT_VERBOSITY)) am__v_CC_0 = @echo " CC " $@; am__v_CC_1 = AM_V_CCLD = $(am__v_CCLD_$(V)) am__v_CCLD_ = $(am__v_CCLD_$(AM_DEFAULT_VERBOSITY)) am__v_CCLD_0 = @echo " CCLD " $@; am__v_CCLD_1 = AM_V_RC = $(am__v_RC_$(V)) am__v_RC_ = $(am__v_RC_$(AM_DEFAULT_VERBOSITY)) am__v_RC_0 = @echo " RC " $@; am__v_RC_1 = And now it is clear why your Makefile doesn't react to setting V: the value zero is hard-coded, and is unaffected by "v=1"! I think the problem is with configure-time detection of whether your Make supports nested variables. The configure script has this: # Check whether --enable-silent-rules was given. if test "${enable_silent_rules+set}" = set; then : enableval=$enable_silent_rules; fi case $enable_silent_rules in yes) AM_DEFAULT_VERBOSITY=0;; no) AM_DEFAULT_VERBOSITY=1;; *) AM_DEFAULT_VERBOSITY=0;; esac am_make=${MAKE-make} { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $am_make supports nested variables" >&5 $as_echo_n "checking whether $am_make supports nested variables... " >&6; } if test "${am_cv_make_support_nested_variables+set}" = set; then : $as_echo_n "(cached) " >&6 else if $as_echo 'TRUE=$(BAR$(V)) BAR0=false BAR1=true V=1 am__doit: @$(TRUE) .PHONY: am__doit' | $am_make -f - >/dev/null 2>&1; then am_cv_make_support_nested_variables=yes else am_cv_make_support_nested_variables=no fi fi { $as_echo "$as_me:${as_lineno-$LINENO}: result: $am_cv_make_support_nested_variables" >&5 $as_echo "$am_cv_make_support_nested_variables" >&6; } if test $am_cv_make_support_nested_variables = yes; then AM_V='$(V)' AM_DEFAULT_V='$(AM_DEFAULT_VERBOSITY)' else AM_V=$AM_DEFAULT_VERBOSITY AM_DEFAULT_V=$AM_DEFAULT_VERBOSITY fi AM_BACKSLASH='\' : ${AM_V=$AM_DEFAULT_VERBOSITY} : ${AM_DEFAULT_V=$AM_DEFAULT_VERBOSITY} Can you look inside config.log and see what did configure find when it ran this fragment? Here it says this: configure:8755: checking whether make supports nested variables configure:8772: result: yes and also configure:3820: checking for GNU Make configure:3870: result: make