kc3-lang/automake/t/suffix8.tap

• Show log

  Commit

• Hash : ffd4ecc9
  Author :
  Date : 2013-05-20T11:23:01
  

  tests: better idiom to override make macro defs on the cmdline
  
  We now do so with a new wrapper shell function 'run_make()', which
  relies on the use of AM_MAKEFLAGS, avoiding the use of the '-e' make
  option.  The use of that option (that causes the environment variables
  to take precedence over the macro definitions in the Makefile) has
  proved to be quite brittle in the past, causing annoying and sometimes
  problematic spurious failures.  This has worsened in some still
  unpublished work going on in development branches.  It's time to solve
  the issue once and for all.
  
  Note that we do not convert all uses of $MAKE in the testsuite right
  away; we might do so in follow-up changes, with leisure, to avoid a
  "patch bomb" effect (this commit is already too much of a bomb itself).
  What we do in this commit is to get rid of all "$MAKE -e" invocations.
  
  We admit that the implementation and feature-set of 'run_make()' are
  far from perfect, but good enough for our current purposes.  We'll
  improve 'run_make()' if and when the need arises.
  
  * syntax-checks.mk (sc_tests_no_make_e): New syntax check, guard against
  the use of "$MAKE -e".
  (syntax_check_rules): Add it.
  (sc_tests_overriding_macros_on_cmdline): Adjust.
  (lint): New, alias for 'maintainer-check', for lazy typists.  Idea
  backported from the 'maint' branch (Automake 1.13a).
  * t/ax/am-test-lib.sh (run_make): New function.  Run $MAKE with the
  given command-line arguments, handling command-line override of variable
  definitions in a smart way (using AM_MAKEFLAGS if a non-GNU make
  implementation is detected to be in use).
  (useless_vpath_rebuild): Adjust to use 'run_make', to avoid a spurious
  maintainer check failure.
  (yl_distcheck): Use 'run_make' rather than bare '$MAKE'.
  (single_quote, append_single_quoted, is_valid_varname): New auxiliary
  function, used, directly or indirectly, by it.
  * Many tests: Adjust to avoid the use of "$MAKE -e", and prefer the
  use of 'run_make' in few other contexts as well, where it makes sense.
  Other minor fixlets while at it.
  
  Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>
  

Download

• t/suffix8.tap

• #! /bin/sh
  # Copyright (C) 2002-2013 Free Software Foundation, Inc.
  #
  # This program 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 2, or (at your option)
  # any later version.
  #
  # This program 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 this program.  If not, see <http://www.gnu.org/licenses/>.
  
  # Test to make sure Automake supports multiple derivations for the
  # same suffix.
  # From PR/37.
  
  required='cc libtoolize'
  . test-init.sh
  
  plan_ 10
  
  cat >>configure.ac <<'END'
  AM_PROG_AR
  AM_PROG_LIBTOOL
  AC_OUTPUT
  END
  
  cat >Makefile.am << 'END'
  # $(LINK) is not defined automatically by Automake, since the *_SOURCES
  # variables don't contain any known extension (.c, .cc, .f ...),
  # So we need this hack.
  LINK = :
  
  bin_PROGRAMS = foo
  lib_LTLIBRARIES = libfoo.la
  
  foo_SOURCES = foo.x_
  libfoo_la_SOURCES = bar.x_
  
  # The elaborate cp commands below account for VPATH issues on
  # weaker make implementations (e.g. IRIX 6.5).
  .x_.y_:
  	cp `test -f '$<' || echo $(srcdir)/`$< $@
  .y_.o:
  	cp `test -f '$<' || echo $(srcdir)/`$< $@
  .y_.obj:
  	cp `test -f '$<' || echo $(srcdir)/`$< $@
  .y_.z_:
  	cp `test -f '$<' || echo $(srcdir)/`$< $@
  .z_.lo:
  	cp `test -f '$<' || echo $(srcdir)/`$< $@
  
  # Some make implementations don't remove intermediate files
  # automatically, thus causing "make distcheck" to fail if
  # this is not added.
  MOSTLYCLEANFILES = *.y_ *.z_
  
  .PHONY: test0 test1 test2
  test0:
  	echo $(foo_OBJECTS) | grep '^foo\.foo$$'
  	echo $(libfoo_la_OBJECTS) | grep '^bar\.lo$$'
  test1:
  	echo $(foo_OBJECTS) | grep '^foo\.$(OBJEXT)$$'
  	echo $(libfoo_la_OBJECTS) | grep '^bar\.lo$$'
  test2: $(foo_OBJECTS) $(libfoo_la_OBJECTS)
  	test -f foo.$(OBJEXT)
  	test -f bar.lo
  check-local: test1 test2
  END
  
  echo 'int main (void) { return 0; }' > foo.x_
  echo 'int bar (void) { return 0; }' > bar.x_
  
  # We must protect the TAP driver from the output of configure, since
  # that might output a stray "ok" on a line of its own (due to a
  # libtool bug on Mac OS X), thus causing a spurious test result to
  # be seen.  See automake bug#11897.
  protect_output ()
  {
    st=0; "$@" >output 2>&1 || st=1
    sed 's/^/  /' output
    test $st -eq 0
  }
  
  command_ok_ "libtoolize" libtoolize
  command_ok_ "aclocal"    $ACLOCAL
  command_ok_ "autoconf"   $AUTOCONF
  command_ok_ "automake"   $AUTOMAKE -a
  command_ok_ "configure"  protect_output ./configure
  command_ok_ "make test0" run_make OBJEXT=foo test0
  command_ok_ "make test1" $MAKE test1
  
  directive=''; make_can_chain_suffix_rules || directive=TODO
  
  for target in test2 all distcheck; do
    command_ok_ "make $target"  \
                -D "$directive" -r "suffix rules not chained" \
                protect_output $MAKE $target
  done
  
  :
  

Download