Re: broken ./configure

[Adam Spiers <adam spiers net>]

Havoc Pennington (hp redhat com) wrote:
> Adam Spiers <adam spiers net> writes:
> > With the latest CVS tree, after generating configure via autogen.sh, I
> > get:
> > 
> > ./configure: ./configure: line 4981: syntax error: unexpected end of file
> > 
> > The script is attached, gzipped.
> 
> Did you have any errors when you ran "autogen.sh", especially aclocal
> errors (near the top of the autogen output)?

No, it went fine.  One departure from normal is that I do

  export ACLOCAL_FLAGS=--acdir=$HOME/local/share/aclocal

because I install a lot of stuff as non-root.  That seemed fine though
(after I'd copied the pkgconfig .m4 stuff there):

$ ./autogen.sh --prefix=~/local
processing .
Running libtoolize...
Running aclocal --acdir=/nfs-home/adams/local/share/aclocal ...
Running autoheader...
Running automake --gnu  ...
Running autoconf ...
Running ./configure --enable-maintainer-mode --enable-compile-warnings --prefix=/nfs-home/adams/local ...
loading cache ./config.cache
checking for a BSD compatible install... (cached) /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... (cached) yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking whether to enable maintainer-specific portions of Makefiles... yes
checking for gcc... (cached) gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for c++... (cached) c++
checking whether the C++ compiler (c++  ) works... yes
checking whether the C++ compiler (c++  ) is a cross-compiler... no
checking whether we are using GNU C++... (cached) yes
checking whether c++ accepts -g... (cached) yes
checking for POSIXized ISC... no
checking for gcc option to accept ANSI C... (cached) none needed
checking how to run the C preprocessor... (cached) gcc -E
checking for ANSI C header files... (cached) yes
checking host system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for ranlib... (cached) ranlib
checking for ld used by GCC... (cached) /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes
checking for BSD-compatible nm... (cached) /usr/bin/nm -B
checking whether ln -s works... (cached) yes
updating cache ./config.cache
loading cache ./config.cache within ltconfig
checking for object suffix... o
checking for executable suffix... (cached) no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC 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 if gcc static flag -static works... -static
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/bin/ld option to reload object files... -r
checking dynamic linker characteristics... 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 for objdir... .libs
creating libtool
loading cache ./config.cache
FYI:  Using default config source xml::${sysconfdir}/gconf/gconf.xml.defaults for schema installation
FYI:  Will build with debugging spew and checks
./configure: line 4981: syntax error: unexpected end of file