bug#18929: feature: output test failures to stdout
Hi, Please have automake automatically dump test logs to stdout for all tests that did not pass. This is becoming more and more important, especially with public CI services like jenkins/travis that retain the stdout/stderr of a build, but not the files generated because this would take up a lot more resources. This can cause frustration when build failures occur with no useful debugging information, for example: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765156 This was previous brought up in the mailing list here: https://lists.gnu.org/archive/html/automake/2013-06/msg00051.html but the solution given is not a very good one for the users of automake (i.e. software developers). It's quite a lot of code to remember, and getting it to work correctly is not obvious. (The solution in that email is a very incomplete solution.) For example, simply overriding check as follows: check: check-am cat test-suite.log does not do the right thing - the log is only output *if the tests all passed*. However, we only really want to see the log if *any test failed*. It is not obvious how to get this working, so automake should do it automatically instead of expecting every user to do it. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git signature.asc Description: OpenPGP digital signature
bug#18929: feature: output test failures to stdout
On 2014-11-02 20:21 +, Ximin Luo wrote: Please have automake automatically dump test logs to stdout for all tests that did not pass. This feature already exists, and is enabled by setting VERBOSE in the environment. For example, VERBOSE=true make check Regards, -- Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
bug#18929: feature: output test failures to stdout
Control: On 03/11/14 16:00, Nick Bowler wrote: On 2014-11-02 20:21 +, Ximin Luo wrote: Please have automake automatically dump test logs to stdout for all tests that did not pass. This feature already exists, and is enabled by setting VERBOSE in the environment. For example, VERBOSE=true make check You're right, this works fine for what I need. I managed to confuse myself by misunderstanding the previously quoted email thread. Sorry for the noise. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git signature.asc Description: OpenPGP digital signature
Building Automake 1.14.1 on mac os x 10.6.8
I am trying to compile Automake on mac os x 10.6.8, but get the following error
message:
forge:automake-1.14.1 boomaxx$ make
cd . /opt/src/automake-1.14.1/t/wrap/automake-1.14 --gnu --ignore-deps
Makefile
Can't locate /opt/src/automake-1.14.1/bin/automake in @INC (@INC contains:
/Library/Perl/Updates/5.10.0
/System/Library/Perl/5.10.0/darwin-thread-multi-2level
/System/Library/Perl/5.10.0 /Library/Perl/5.10.0/darwin-thread-multi-2level
/Library/Perl/5.10.0 /Network/Library/Perl/5.10.0/darwin-thread-multi-2level
/Network/Library/Perl/5.10.0 /Network/Library/Perl
/System/Library/Perl/Extras/5.10.0/darwin-thread-multi-2level
/System/Library/Perl/Extras/5.10.0 .) at
/opt/src/automake-1.14.1/t/wrap/automake-1.14 line 27.
make: *** [Makefile.in] Error 2
Following commands I've entered:
Download copy (Browser Safari Version 5.1.10 (6534.59.10):
http://ftp.gnu.org/gnu/automake/
gzip -d
tar
cp -R automake-1.14.1 /opt/src
Build:
./configure
make
./configure runs without any problems, so far as I can see:
forge:automake-1.14.1 boomaxx$ ./configure
checking whether make supports nested variables... yes
checking build system type... x86_64-apple-darwin10.8.0
checking host system type... x86_64-apple-darwin10.8.0
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... lib/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether ln -s works... yes
checking for perl... /usr/bin/perl
checking for tex... no
checking for yacc... yacc
checking for lex... lex
checking whether autoconf is installed... yes
checking whether autoconf works... yes
checking whether autoconf is recent enough... yes
checking whether ln works... yes
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
configure: will now look for a sturdy POSIX shell, for our testsuite
checking for sh... /bin/sh
checking for sh5... no
checking for dash... no
checking for ash... no
checking for bash... /bin/bash
checking for zsh... /bin/zsh
checking for ksh... /bin/ksh
checking for pdksh... no
checking whether /bin/sh supports $(cmd)... yes
checking whether /bin/sh supports $((expr))... yes
checking whether /bin/sh supports ${#var}... yes
checking whether /bin/sh supports ${var#glob} and ${var%glob}... yes
checking whether /bin/sh preserves exit traps with set -e... yes
checking whether /bin/sh can define exit traps in a shell function... yes
checking whether /bin/sh corrupts stderr with set -x... no
checking whether /bin/sh can return early from dot-sourced files... yes
checking whether /bin/sh supports alias named like shell builtins... yes
checking whether /bin/sh supports test -e... yes
configure: shell /bin/sh is good enough, stop looking
configure: will use /bin/sh as the testsuite shell
configure: will now look for generic compilers
checking for cc... cc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether cc accepts -g... yes
checking for cc option to accept ISO C89... none needed
checking whether cc understands -c and -o together... yes
checking for aCC... no
checking for FCC... no
checking for KCC... no
checking for xlC_r... no
checking for xlC... no
checking for c++... c++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether c++ accepts -g... yes
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgfortran... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking for nagfor... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for g95... no
checking for gfortran... no
checking whether the Fortran compiler works... no
configure: WARNING: Fortran compiler cannot create executables
configure: tests requiring the Fortran compiler will be skipped
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for g77... no
checking for gfortran... no
checking whether the Fortran 77 compiler works... no
configure: WARNING: Fortran 77 compiler cannot create executables
configure: tests requiring the
Macro to select c++ as default compiler for c files.
Hi All, I am working with autotools and i wish to use c++ compiler by default for compiling my c files. USUAL behaviour : ex : myexecutable_SOURCES = file.cpp - uses c++ compiler myexecutable_SOURCES = file.c - uses c compiler (myexecutable_SOURCES is defined in my Makefile.am) Expected behaviour : ex : myexecutable_SOURCES = file.cpp - uses c++ compiler myexecutable_SOURCES = file.c - SHOULD USE c++ compiler (myexecutable_SOURCES is defined in my Makefile.am) I tried using AC_PROG_CC([c++]) and AC_LANG([C++]) in my configure.ac but its still using c compiler. Can anyone please let me know how to use c++ compiler as default for compiling my c files. Thanks Regards, Lakshmi M
Re: Macro to select c++ as default compiler for c files.
On 3 November 2014 11:28, Lakshmi M laksh...@tataelxsi.co.in wrote: Hi All, I am working with autotools and i wish to use c++ compiler by default for compiling my c files. USUAL behaviour : ex : myexecutable_SOURCES = file.cpp - uses c++ compiler myexecutable_SOURCES = file.c - uses c compiler (myexecutable_SOURCES is defined in my Makefile.am) Expected behaviour : ex : myexecutable_SOURCES = file.cpp - uses c++ compiler myexecutable_SOURCES = file.c - SHOULD USE c++ compiler (myexecutable_SOURCES is defined in my Makefile.am) I think that Automake simply matches on the file name extension. If you cannot rename the source files to have one of the common C++ source file extensions (.C, .cxx, .c++, .cc) then you will have to supply compiler specific flags, I think, like the GCC's `-x c++`. I tried using AC_PROG_CC([c++]) and AC_LANG([C++]) in my configure.ac but its still using c compiler. Can anyone please let me know how to use c++ compiler as default for compiling my c files. -- VZ
Re: Macro to select c++ as default compiler for c files.
On Mon, Nov 03, 2014 at 03:58:14PM +0530, Lakshmi M wrote: Can anyone please let me know how to use c++ compiler as default for compiling my c files. One way would be to have, anywhere in your makefiles: CC = $(CXX) That would compile *all* C as C++. signature.asc Description: Digital signature
