emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Any idea why "make V=1" isn't working for me?


From: Eli Zaretskii
Subject: Re: Any idea why "make V=1" isn't working for me?
Date: Sat, 10 Oct 2015 15:23:42 +0300

> From: Juanma Barranquero <address@hidden>
> Date: Sat, 10 Oct 2015 13:32:34 +0200
> Cc: Emacs developers <address@hidden>
> 
> > 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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]