bug-autoconf
[Top][All Lists]
Advanced

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

Bug in autoconf 2.53


From: Jens Krüger
Subject: Bug in autoconf 2.53
Date: Thu, 20 Jun 2002 16:23:34 +0200

Hi,

it takes me a long time to find the following bug. I used the following 
configure.in:

AC_INIT(TestFilterClass, 0.0.0, address@hidden)
AC_PREREQ(2.52)
AC_COPYRIGHT([(c) Jens Krüger])
AC_CONFIG_SRCDIR(main.cpp)
AC_CONFIG_AUX_DIR(config)
AM_INIT_AUTOMAKE([1.6])

AM_PROG_LIBTOOL
AC_PROG_CXX
AC_ISC_POSIX

AM_CONFIG_HEADER(config.h)

AM_PROG_LIBTOOL
AC_STDC_HEADERS

AC_PROG_MAKE_SET

CXXFLAGS="$CXX_FLAGS -g -Wall -D_REENTRANT -D_GNU_SOURCE"
AC_SUBST(CFLAGS)

QTDIR=${QTDIR-/usr/local/qt}
AC_SUBST(QTDIR)
MOC=${QTDIR}/bin/moc
AC_SUBST(MOC)

UIC=${QTDIR)/bin/uic
AC_SUBST(UIC)

AC_PREFIX_DEFAULT(${DAVEROOT-/usr/local})

NEXUSROOT=${NEXUSROOT-/usr/local/NeXus}
AC_SUBST(NEXUSROOT)

HDFROOT=${HDFROOT-/usr/local/hdf}
AC_SUBST(HDFROOT)

imagedir=${DAVEROOT-/usr/local}"/share/openDaVE"
AC_SUBST(imagedir)

AC_ARG_ENABLE(debug, [  --enable-debug        enable debug output of the 
modules default=no],
                [CXXFLAGS="$CXXFLAGS -D_DEBUG"], [])

AC_CONFIG_FILES(Makefile)
AC_OUTPUT

running the following commands:

touch ChangeLog
touch NEWS
aclocal -I config
autoheader
libtoolize --force --copy --automake
automake --add-missing --copy --include-deps 
autoconf

running configure I got the following output:

checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking dependency style of gcc... gcc
checking for ld used by GCC... /usr/i486-suse-linux/bin/ld
checking if the linker (/usr/i486-suse-linux/bin/ld) is GNU ld... yes
checking for /usr/i486-suse-linux/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/i486-suse-linux/bin/ld) supports shared 
libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc
checking for strerror in -lcposix... no
checking for ANSI C header files... (cached) yes
checking whether make sets ${MAKE}... (cached) yes
./configure: line 8039: syntax error near unexpected token `&/'
./configure: line 8039: `     s/^\([^=]*\)=\(.*[{}].*\)$/test "${\1+set}" = 
set || &/'

I could not understand what's the reason for this mysterious message. After a 
lot of hours I found the reason:

Instead of 

UIC=${QTDIR}/bin/uic

I wrote

UIC=${QTDIR)/bin/uic

I guess this bug is very difficult to find and occur rarly, but it should be 
fixed in one of the next releases.

Regards

Jens

-- 

Jens Krüger

Technische Universität München
ZWE FRM-II

Lichtenberg-Str. 1
D-85747 Garching

Tel: + 49 89 289 14 716
Fax: + 49 89 289 14 666
mailto:address@hidden
http://www.frm2.tu-muenchen.de



reply via email to

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