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

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

[Juanma Barranquero]

[-- Attachment #1: Type: text/plain, Size: 542 bytes --]

Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
$ which make
/bin/make.exe

Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
$ echo $PATH
.:/c/Devel/emacs/build/bin:/bin:/mingw/bin:/c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/bin64/Git/cmd

Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
$ rm runemacs.exe

Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
$ make V=1 runemacs.exe
  CCLD     runemacs.exe
[plus a few of warnings about things in runemacs]

Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt


Shouldn't "make V=1" show the full command?

[-- Attachment #2: Type: text/html, Size: 825 bytes --]

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

[Paul Eggert]

Juanma Barranquero wrote:
> Shouldn't "make V=1" show the full command?

Possibly it's your 'make' implementation. 'make V=1' is more-verbose only if 
your 'make' groks nested variable expansions (a GNU extension to POSIX). If your 
'make' doesn't support this feature, the 'V=1' is ineffective, and you have to 
enable verbosity at configure-time instead. By default, verbosity is disabled 
because Emacs's configure.ac contains 'AM_SILENT_RULES([yes])'; if you are using 
a non-GNU 'make' and want verbose output you can configure with './configure 
--disable-silent-rules'.

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

[Eli Zaretskii]

> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Fri, 9 Oct 2015 22:07:47 -0700
> 
> Juanma Barranquero wrote:
> > Shouldn't "make V=1" show the full command?
> 
> Possibly it's your 'make' implementation. 'make V=1' is more-verbose only if 
> your 'make' groks nested variable expansions (a GNU extension to POSIX). If your 
> 'make' doesn't support this feature, the 'V=1' is ineffective, and you have to 
> enable verbosity at configure-time instead. By default, verbosity is disabled 
> because Emacs's configure.ac contains 'AM_SILENT_RULES([yes])'; if you are using 
> a non-GNU 'make' and want verbose output you can configure with './configure 
> --disable-silent-rules'.

The MS-Windows build always uses GNU Make, so this is not the reason.

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

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Fri, 9 Oct 2015 11:53:49 +0200
> 
> Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
> $ which make
> /bin/make.exe
> 
> Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
> $ echo $PATH
> .:/c/Devel/emacs/build/bin:/bin:/mingw/bin:/c/WINDOWS/system32:/c/WINDOWS:/c/WINDOWS/System32/Wbem:/c/bin64/Git/cmd
> 
> Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
> $ rm runemacs.exe
> 
> Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
> $ make V=1 runemacs.exe
> CCLD runemacs.exe
> [plus a few of warnings about things in runemacs]
> 
> Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
> 
> Shouldn't "make V=1" show the full command?

Yes, it should.  It does for me:

  Zaretzky@home-c4e4a596f7 /d/gnu/git/emacs/trunk
  $ cd nt

  Zaretzky@home-c4e4a596f7 /d/gnu/git/emacs/trunk/nt
  $ rm runemacs.exe

  Zaretzky@home-c4e4a596f7 /d/gnu/git/emacs/trunk/nt
  $ make V=1
  gcc -std=gnu99  -mtune=pentium4      -I. -I.   -mtune=pentium4   -DUSE_CRT_DLL=1 -I /d/gnu/git/emacs/trunk/nt/inc -gdwarf-4 -g3 -O0 runemacs.c emacs.res -mwindows -o runemacs.exe

What does "make --version" show in the MSYS Bash session?  My says:

  $ make --version
  GNU Make 3.82.90
  Built for i686-pc-msys
  Copyright (C) 2010  Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

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

[Juanma Barranquero]

[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]

On Sat, Oct 10, 2015 at 10:51 AM, Eli Zaretskii <eliz@gnu.org> wrote:

> What does "make --version" show in the MSYS Bash session?  My says:
>
>   $ make --version
>   GNU Make 3.82.90
>   Built for i686-pc-msys
>   Copyright (C) 2010  Free Software Foundation, Inc.
>   License GPLv3+: GNU GPL version 3 or later <
http://gnu.org/licenses/gpl.html>
>   This is free software: you are free to change and redistribute it.
>   There is NO WARRANTY, to the extent permitted by law.

The same. I got that make.exe from
https://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/
as pero nt/INSTALL instructions.

Juanma@ODIEONE /c/Devel/emacs/repo/trunk
$ cd nt

Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
$ rm runemacs.exe

Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
$ make V=1
  CCLD     runemacs.exe

Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
$ make --version
GNU Make 3.82.90
Built for i686-pc-msys
Copyright (C) 2010  Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

[-- Attachment #2: Type: text/html, Size: 1613 bytes --]

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

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sat, 10 Oct 2015 12:08:59 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> > What does "make --version" show in the MSYS Bash session? My says:
> >
> > $ make --version
> > GNU Make 3.82.90
> > Built for i686-pc-msys
> > Copyright (C) 2010 Free Software Foundation, Inc.
> > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> > This is free software: you are free to change and redistribute it.
> > There is NO WARRANTY, to the extent permitted by law.
> 
> The same. I got that make.exe from
> https://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/ as
> pero nt/INSTALL instructions.
> 
> Juanma@ODIEONE /c/Devel/emacs/repo/trunk
> $ cd nt
> 
> Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
> $ rm runemacs.exe
> 
> Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
> $ make V=1
> CCLD runemacs.exe
> 
> Juanma@ODIEONE /c/Devel/emacs/repo/trunk/nt
> $ make --version
> GNU Make 3.82.90
> Built for i686-pc-msys
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.

Weird.

Can you post your nt/Makefile?

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

[Juanma Barranquero]

[-- Attachment #1.1: Type: text/plain, Size: 114 bytes --]

On Sat, Oct 10, 2015 at 1:10 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> Can you post your nt/Makefile?

Attached.

[-- Attachment #1.2: Type: text/html, Size: 219 bytes --]

[-- Attachment #2: Makefile --]
[-- Type: application/octet-stream, Size: 9924 bytes --]

### nt/Makefile.  Generated from Makefile.in by configure.

# Copyright (C) 2013-2015 Free Software Foundation, Inc.

# This file is part of GNU Emacs.

# GNU Emacs is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.

# GNU Emacs is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.

# You should have received a copy of the GNU General Public License
# along with GNU Emacs.  If not, see <http://www.gnu.org/licenses/>.

# Avoid trouble on systems where the `SHELL' variable might be
# inherited from the environment.
SHELL = /bin/sh

# ==================== Things `configure' will edit ====================

CC=gcc -std=gnu99 
CFLAGS=-O0 -g3 -Wno-error -Wno-pointer-sign -Wno-missing-prototypes -Wno-missing-declarations -Wunused-parameter
CPPFLAGS = -mtune=pentium4  -Ic:/Devel/emacs/include -DUSE_CRT_DLL=1 -I ${abs_top_srcdir}/nt/inc
LDFLAGS = -Lc:/Devel/emacs/lib

version=25.0.50
## Used in $archlibdir.
configuration=i686-pc-mingw32
EXEEXT=.exe
C_SWITCH_SYSTEM=-mtune=pentium4
C_SWITCH_MACHINE=
PROFILING_CFLAGS = 
WARN_CFLAGS =  -W -Wabi -Waddress -Waggressive-loop-optimizations -Wall -Wattributes -Wbuiltin-macro-redefined -Wcast-align -Wchar-subscripts -Wclobbered -Wcomment -Wcomments -Wcoverage-mismatch -Wcpp -Wdeprecated -Wdeprecated-declarations -Wdisabled-optimization -Wdiv-by-zero -Wdouble-promotion -Wempty-body -Wendif-labels -Wenum-compare -Wextra -Wformat-contains-nul -Wformat-extra-args -Wformat-security -Wformat-y2k -Wformat-zero-length -Wfree-nonheap-object -Wignored-qualifiers -Wimplicit -Wimplicit-function-declaration -Wimplicit-int -Winit-self -Wint-to-pointer-cast -Winvalid-memory-model -Winvalid-pch -Wlogical-op -Wmain -Wmaybe-uninitialized -Wmissing-braces -Wmissing-declarations -Wmissing-include-dirs -Wmissing-parameter-type -Wmissing-prototypes -Wmultichar -Wnarrowing -Wnested-externs -Wnonnull -Wold-style-declaration -Wold-style-definition -Woverflow -Woverride-init -Wpacked -Wpacked-bitfield-compat -Wparentheses -Wpointer-arith -Wpointer-sign -Wpointer-to-int-cast -Wpragmas -Wreturn-local-addr -Wreturn-type -Wsequence-point -Wsizeof-pointer-memaccess -Wstrict-aliasing -Wstrict-prototypes -Wsuggest-attribute=format -Wsuggest-attribute=noreturn -Wtrampolines -Wtrigraphs -Wuninitialized -Wunknown-pragmas -Wunused -Wunused-but-set-parameter -Wunused-but-set-variable -Wunused-function -Wunused-label -Wunused-local-typedefs -Wunused-macros -Wunused-result -Wunused-value -Wunused-variable -Wvarargs -Wvariadic-macros -Wvector-operation-performance -Wvolatile-register-var -Wwrite-strings -Wnormalized=nfc -Wredundant-decls -Wno-missing-field-initializers -Wno-sign-compare -Wno-type-limits -Wno-unused-parameter -Wno-format-nonliteral
WERROR_CFLAGS =  -Werror

# Program name transformation.
TRANSFORM = s,x,x,

# '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 =

# ==================== Where To Install Things ====================

# The default location for installation.  Everything is placed in
# subdirectories of this directory.  The default values for many of
# the variables below are expressed in terms of this one, so you may
# not need to change them.  This is set with the --prefix option to
# `../configure'.
prefix=/c/Devel/emacs/repo/trunk

# Like `prefix', but used for architecture-specific files.  This is
# set with the --exec-prefix option to `../configure'.
exec_prefix=${prefix}

# Where to install Emacs and other binaries that people will want to
# run directly (like etags).  This is set with the --bindir option
# to `../configure'.
bindir=${exec_prefix}/bin

# The root of the directory tree for read-only architecture-independent
# data files.  ${datadir}, ${infodir} and ${mandir} are based on this.
datarootdir=${prefix}/share

# Where to install architecture-independent data files.  ${lispdir}
# and ${etcdir} are subdirectories of this.  This is set with the
# --datadir option to `../configure'.
datadir=${datarootdir}

# Where to install and expect executable files to be run by Emacs
# rather than directly by users, and other architecture-dependent
# data.  ${archlibdir} is usually below this.  This is set with the
# --libexecdir option to `../configure'.
libexecdir=${exec_prefix}/libexec

# Directory for local state files for all programs.
localstatedir=${prefix}/var

# Where to find the source code.  This is set by the configure
# script's `--srcdir' option.  However, the value of ${srcdir} in
# this makefile is not identical to what was specified with --srcdir,
# since the variable here has `/lib-src' added at the end.

# We use $(srcdir) explicitly in dependencies so as not to depend on VPATH.
srcdir=.


# The top-level source directory, also set by configure.
top_srcdir=..
# MinGW CPPFLAGS may use this.
abs_top_srcdir=/c/Devel/emacs/repo/trunk

# ==================== Emacs-specific directories ====================

# These variables hold the values Emacs will actually use.  They are
# based on the values of the standard Make variables above.

# Where to put executables to be run by Emacs rather than the user.
# This path usually includes the Emacs version and configuration name,
# so that multiple configurations for multiple versions of Emacs may
# be installed at once.  This can be set with the --archlibdir option
# to `../configure'.
archlibdir=${libexecdir}/emacs/${version}/${configuration}

# ==================== Utility Programs for the Build =================

# ../configure figures out the correct values for these.
INSTALL = /bin/install -c
INSTALL_DATA = ${INSTALL} -m 644
INSTALL_PROGRAM = ${INSTALL}
INSTALL_SCRIPT = ${INSTALL}
# By default, we uphold the dignity of our programs.
INSTALL_STRIP =
MKDIR_P = /bin/mkdir -p

# ========================== Lists of Files ===========================

# Things that a user might actually run, which should be installed in bindir.
INSTALLABLES = runemacs${EXEEXT} addpm${EXEEXT}

# Things that Emacs runs internally, which should not be installed in bindir.
UTILITIES = cmdproxy${EXEEXT} ddeclient${EXEEXT}

# Things that Emacs runs during the build process.
DONT_INSTALL =

# All files that are created by the linker, i.e., whose names end in ${EXEEXT}.
EXE_FILES = ${INSTALLABLES} ${UTILITIES} ${DONT_INSTALL}

# =========================== Configuration ===========================

# MS-Windows resource files and resource compiler
EMACSRES = emacs.res
EMACS_MANIFEST = emacs-x86.manifest
WINDRES = windres

## Extra libraries to use when linking addpm.
LIBS_ADDPM = -lole32 -luuid

## Compilation and linking flags
BASE_CFLAGS = $(C_SWITCH_SYSTEM) $(C_SWITCH_MACHINE) \
	      $(WARN_CFLAGS) $(WERROR_CFLAGS) \
	      -I. -I${srcdir}

ALL_CFLAGS = ${BASE_CFLAGS} ${PROFILING_CFLAGS} ${LDFLAGS} ${CPPFLAGS} ${CFLAGS}
## Unused.
LINK_CFLAGS = ${BASE_CFLAGS} ${LDFLAGS} ${CFLAGS}
## Unused.
CPP_CFLAGS = ${BASE_CFLAGS} ${PROFILING_CFLAGS} ${CPPFLAGS} ${CFLAGS}

all: ${EXE_FILES}

.PHONY: all

## Install the internal utilities.  Until they are installed, we can
## just run them directly from nt/.
$(DESTDIR)${archlibdir}: all
	@echo
	@echo "Installing utilities run internally by Emacs."
	umask 022; ${MKDIR_P} "$(DESTDIR)${archlibdir}"
	exp_archlibdir=`cd "$(DESTDIR)${archlibdir}" && /bin/pwd`; \
	if [ "$$exp_archlibdir" != "`/bin/pwd`" ]; then \
	  for file in ${UTILITIES}; do \
	    $(INSTALL_PROGRAM) $(INSTALL_STRIP) $$file "$(DESTDIR)${archlibdir}/$$file" ; \
	  done ; \
        fi

.PHONY: install uninstall mostlyclean clean distclean maintainer-clean
.PHONY: bootstrap-clean extraclean check tags

install: $(DESTDIR)${archlibdir}
	@echo
	@echo "Installing utilities for users to run."
	umask 022; ${MKDIR_P} "$(DESTDIR)${bindir}"
	for file in ${INSTALLABLES} ; do \
	  $(INSTALL_PROGRAM) $(INSTALL_STRIP) $${file} "$(DESTDIR)${bindir}"/`echo $${file} | sed -e 's/${EXEEXT}$$//' -e '$(TRANSFORM)'`${EXEEXT} ; \
	done
	${MKDIR_P} "$(DESTDIR)${datadir}/emacs/$(version)"
	$(INSTALL_DATA) ${srcdir}/README.W32 "$(DESTDIR)${datadir}/emacs/$(version)"

uninstall:
	rm -f "$(DESTDIR)${datadir}/emacs/$(version)/README.W32"
	for file in ${INSTALLABLES}; do \
	  rm -f "$(DESTDIR)${bindir}"/`echo $${file} | sed -e 's/${EXEEXT}$$//' -e '$(TRANSFORM)'`${EXEEXT} ; \
	done
	if [ -d "$(DESTDIR)${archlibdir}" ]; then \
	  (cd "$(DESTDIR)${archlibdir}" && rm -f ${UTILITIES}) \
	fi

mostlyclean:
	-rm -f core *.o *.res

clean: mostlyclean
	-rm -f ${EXE_FILES}

distclean: clean
	-rm -f TAGS Makefile *.rc

bootstrap-clean maintainer-clean: distclean
	true

extraclean: maintainer-clean
	-rm -f *~ \#*

## Test the contents of the directory.
check:
	@echo "We don't have any tests for the nt/ directory yet."

tags: TAGS
TAGS: ${EXE_FILES:${EXEEXT}=.c}
	../lib-src/etags *.[ch]

## Build the programs
addpm${EXEEXT}: ${srcdir}/addpm.c ../src/epaths.h
	$(AM_V_CCLD)$(CC) ${ALL_CFLAGS} $< $(LIBS_ADDPM) -o $@

ddeclient${EXEEXT}: ${srcdir}/ddeclient.c
	$(AM_V_CCLD)$(CC) ${ALL_CFLAGS} $< -o $@

cmdproxy${EXEEXT}: ${srcdir}/cmdproxy.c
	$(AM_V_CCLD)$(CC) ${ALL_CFLAGS} $< -o $@

runemacs${EXEEXT}: ${srcdir}/runemacs.c $(EMACSRES)
	$(AM_V_CCLD)$(CC) ${ALL_CFLAGS} $^ -mwindows -o $@

## Also used in ../src/Makefile.
emacs.res ../src/emacs.res: emacs.rc ${srcdir}/icons/emacs.ico \
  ${srcdir}/icons/hand.cur ${srcdir}/$(EMACS_MANIFEST)
	$(AM_V_RC)${WINDRES} -I ${srcdir} -O coff -o $@ $<

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

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sat, 10 Oct 2015 13:32:34 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> > 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

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

[Juanma Barranquero]

[-- Attachment #1.1: Type: text/plain, Size: 583 bytes --]

On Sat, Oct 10, 2015 at 2:23 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> 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

I don't have that in my config.log, just

am_cv_make_support_nested_variables=yes

(that's the only reference to nested variables in all of config.log)

>   configure:3820: checking for GNU Make
>   configure:3870: result: make

configure:3840: checking for GNU Make
configure:3890: result: make

[-- Attachment #1.2: Type: text/html, Size: 880 bytes --]

[-- Attachment #2: config.log.gz --]
[-- Type: application/x-gzip, Size: 58426 bytes --]

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

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sat, 10 Oct 2015 15:19:02 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> > 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
> 
> I don't have that in my config.log, just
> 
> am_cv_make_support_nested_variables=yes

Do you have the fragment below in configure?  Does it immediately
precede the test "whether ln -s works for files in the same
directory"?



  # 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}

If you do have this fragment, please try to figure out why it doesn't
get executed.  FWIW, I've just ran configure with exactly the same
options as you, and I still don't get the same result in nt/Makefile.

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

[Juanma Barranquero]

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

Lines 8758:8783 from mi configure file:

# 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_BACKSLASH='\'

: ${AM_V=$AM_DEFAULT_VERBOSITY}
: ${AM_DEFAULT_V=$AM_DEFAULT_VERBOSITY}









{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether ln -s works for
files in the same directory" >&5
$as_echo_n "checking whether ln -s works for files in the same directory...
" >&6; }
rm -f conf$$ conf$$.file
​

[-- Attachment #2: Type: text/html, Size: 1047 bytes --]

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

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sat, 10 Oct 2015 16:18:26 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> Lines 8758:8783 from mi configure file:
> 
> # 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_BACKSLASH='\'
> 
> : ${AM_V=$AM_DEFAULT_VERBOSITY}
> : ${AM_DEFAULT_V=$AM_DEFAULT_VERBOSITY}
> 
> { $as_echo "$as_me:${as_lineno-$LINENO}: checking whether ln -s works for files
> in the same directory" >&5
> $as_echo_n "checking whether ln -s works for files in the same directory... "
> >&6; }
> rm -f conf$$ conf$$.file

A whole section is missing!

Do you have silent.m4 in share/aclocal-1.11/ ?  If not, which version
of Automake did you install, and where did you get it from?

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

[Juanma Barranquero]

[-- Attachment #1: Type: text/plain, Size: 383 bytes --]

On Sat, Oct 10, 2015 at 4:32 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> Do you have silent.m4 in share/aclocal-1.11/ ?

Yes

> If not, which version
> of Automake did you install, and where did you get it from?

automake-11

It's the MinGW version. I used the GUI installer and it came along for the
ride, and autogen.sh seemed to work, so I didn't search for another version.

   J

[-- Attachment #2: Type: text/html, Size: 604 bytes --]

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

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sat, 10 Oct 2015 16:53:50 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> > Do you have silent.m4 in share/aclocal-1.11/ ?
> 
> Yes

Is that the MinGW share/aclocal-1.11, or the MSYS share/aclocal-1.11?
It should be the latter.

> > If not, which version
> > of Automake did you install, and where did you get it from?
> 
> automake-11
> 
> It's the MinGW version. I used the GUI installer and it came along for the
> ride, and autogen.sh seemed to work, so I didn't search for another version.

The MinGW packages of Autoconf and Automake are not useful, I suggest
to remove them.  Or leave them alone, if you want, but install this
one as well:

  http://sourceforge.net/projects/ezwinports/files/automake-1.11.6-msys-bin.zip/download

There's Autoconf there, I suggest to install that as well.

Please note that README.txt says to unzip both from the root of the
MSYS tree, not the MinGW tree.

I believe this is your problem: Automake didn't find silent.m4, or
perhaps the contents of that file is incorrect.  The missing section
of configure is taken from that file.

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

[Juanma Barranquero]

[-- Attachment #1: Type: text/plain, Size: 283 bytes --]

On Sat, Oct 10, 2015 at 5:33 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> I believe this is your problem: Automake didn't find silent.m4, or
> perhaps the contents of that file is incorrect.  The missing section
> of configure is taken from that file.

Yes, it is working now. Thanks.

[-- Attachment #2: Type: text/html, Size: 406 bytes --]

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

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sun, 11 Oct 2015 01:57:44 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> On Sat, Oct 10, 2015 at 5:33 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> > I believe this is your problem: Automake didn't find silent.m4, or
> > perhaps the contents of that file is incorrect. The missing section
> > of configure is taken from that file.
> 
> Yes, it is working now. Thanks.

Great.

Do you see something that should be changed in nt/INSTALL to make such
problems less probable?

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

[Juanma Barranquero]

[-- Attachment #1: Type: text/plain, Size: 460 bytes --]

On Sun, Oct 11, 2015 at 5:03 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> Do you see something that should be changed in nt/INSTALL to make such
> problems less probable?

When nt/INSTALL mentions automake/autoconf, perhaps there should be a note
like your comment:

    The MinGW packages of Autoconf and Automake are not useful, I
suggest to remove them.

because if you're using the MinGW installer, it's quite easy to end with
MinGW versions of these tools.

[-- Attachment #2: Type: text/html, Size: 635 bytes --]

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

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Mon, 12 Oct 2015 03:50:36 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> > Do you see something that should be changed in nt/INSTALL to make such
> > problems less probable?
> 
> When nt/INSTALL mentions automake/autoconf, perhaps there should be a note like
> your comment:
> 
> The MinGW packages of Autoconf and Automake are not useful, I suggest to remove
> them.
> 
> because if you're using the MinGW installer, it's quite easy to end with MinGW
> versions of these tools.

Done.