[Top][All Lists]

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


From: Robert Collins
Subject: pr19.test
Date: Tue, 13 Mar 2001 08:47:05 +1100

    I've altered pr19.test to be (added VERBOSE=yes, and AC_EXEEXT &&
AC_OBJEXT). I've tried this test on both openBSD & windows. It's failing
on both (unaltered on openBSD as it doesn't have the .exe headache).

I'm quite happy to commit some time to troubleshooting this, if you folk
want to steer me (I've not looked under the hood at the autotools except
in the most superficial way.

What is the minimum requirements for automake CVS as far as the other
autotools go? I.E. what should I install on my system before automake?


#! /bin/sh

# Test associated with PR 19.
# From Matthew D. Langston.


. $srcdir/defs || exit 1

cat > << 'END'
dnl Prevent automake from looking in .. and ../..
AM_INIT_AUTOMAKE(am_lex_bug, 0.1.1)

dnl Checks for programs.


cat > << 'END'
LDADD             = @LEXLIB@

noinst_PROGRAMS   = foo
foo_SOURCES       = foo.l

echo %% > foo.l

# Fail gracefully if no autoconf.

# Likewise for gcc.
(gcc -v) > /dev/null 2>&1 || exit 77

# Likewise for gzip.
(gzip --version) > /dev/null 2>&1 || exit 77

$ACLOCAL || exit 1
$AUTOCONF || exit 1
$AUTOMAKE -a || exit 1
CC=gcc ./configure || exit 1
$MAKE || exit 1
$MAKE distcheck || exit 1

gunzip am_lex_bug-0.1.1.tar.gz || exit 1

tar tf am_lex_bug-0.1.1.tar | fgrep foo.c

the test output follows

$ make check
make  check-TESTS
make[1]: Entering directory `/usr/src/automake/tests'
=== Running test ./subdirbuiltsources.test warning: AC_ARG_PROGRAM invoked multiple times
automake: installing `./install-sh'
automake: installing `./mkinstalldirs'
automake: installing `./missing'
automake: installing `./INSTALL'
automake: installing `./NEWS'
automake: installing `./README'
automake: installing `./COPYING'
automake: installing `./AUTHORS'
automake: installing `./ChangeLog'
checking for a BSD compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for mawk... no
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking whether make sets ${MAKE}... (cached) yes
checking for a BSD compatible install... /bin/install -c
checking for ranlib... ranlib
checking for gcc... gcc
checking for C compiler default output... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for executable suffix... .exe
checking for object suffix... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for style of include used by make... #
checking dependency style of gcc... gcc
configure: creating ./config.status
config.status: creating Makefile
config.status: creating lib/Makefile
make[2]: Entering directory `/usr/src/automake/tests/testSubDir'
Making all in lib
make[3]: Entering directory `/usr/src/automake/tests/testSubDir/lib'
echo \#define FOO_DEFINE 1 >foo.h
make  all-am
make[4]: Entering directory `/usr/src/automake/tests/testSubDir/lib'
gcc -g -O2   -c -o foo.o foo.c
foo.c:1: foo.h: No such file or directory
make[4]: *** [foo.o] Error 1
make[4]: Leaving directory `/usr/src/automake/tests/testSubDir/lib'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/usr/src/automake/tests/testSubDir/lib'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/automake/tests/testSubDir'
FAIL: subdirbuiltsources.test
1 of 1 tests failed
make[1]: *** [check-TESTS] Error 1
make[1]: Leaving directory `/usr/src/automake/tests'
make: *** [check-am] Error 2

> Still, I shall repeat myself: to launch the *dignified* handling of
> EXEEXT and OBJEXT in Automake (not the Unix centrist default you
> changed)), you need to use AC_EXEEXT and AC_OBJEXT in the
>  Then, again, the proper fix for the test failure you
> observe consists in fixing in the *test*.

reply via email to

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