[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
conftest problem using autoconf 2.13-14
From: |
Elisabetta Ronchieri |
Subject: |
conftest problem using autoconf 2.13-14 |
Date: |
Tue, 28 May 2002 16:28:16 +0200 |
Hi,
I am working on RH 7.2 and using the following autotool:
autoconf 2.13-14
automake 1.4p5-2
libtool 1.4-8
The autogen.sh script is reported below:
#! /bin/sh
set -x
if [ ! -d ./config ]; then
mkdir ./config
fi
rm -f config.cache
aclocal -I config
touch NEWS README AUTHORS ChangeLog
libtoolize --ltdl --force --copy
autoheader
automake --foreign -a -c -i --add-missing
autoconf
During its execution I receive the following message:
./bootstrap
+ '[' '!' -d ./config ']'
+ mkdir ./config
+ rm -f config.cache
+ aclocal -I config
+ touch NEWS README AUTHORS ChangeLog
+ libtoolize --ltdl --force --copy
You should update your `aclocal.m4' by running aclocal.
Putting files in AC_CONFIG_AUX_DIR, `config'.
+ autoheader
+ automake --foreign -a -c -i --add-missing
automake: configure.in: installing `config/install-sh'
automake: configure.in: installing `config/mkinstalldirs'
automake: configure.in: installing `config/missing'
+ autoconf
Why is there the message: You should update your `aclocal.m4' by running
aclocal.??
How can I do to remove it??
The configure.in file is reported below:
dnl
dnl Process this file with autoconf to produce a configure script
dnl
AC_INIT(test/remove1.cpp)
dnl
dnl Declare the package
dnl
PACKAGE=C++
VERSION=1.0.0
AC_SUBST(PACKAGE)
AC_SUBST(VERSION)
dnl
dnl Set config options
dnl
AC_CONFIG_AUX_DIR(config)
dnl AM_CONFIG_HEADER(config.h)
AM_INIT_AUTOMAKE($PACKAGE, $VERSION)
ISODATE=`date +%Y-%m-%d`
AC_SUBST(ISODATE)
dnl
dnl Checks for programs
dnl
AC_PROG_CXX
AC_PROG_AWK
AC_PROG_CC
AC_PROG_INSTALL
AC_PROG_LN_S
dnl
dnl Checks for use of libtool
dnl
AM_PROG_LIBTOOL
dnl
dnl Define required variables
dnl
AC_SUBST(SUBDIRS)
AC_SUBST(LIBTOOL_DEPS)
AC_OUTPUT([
test/Makefile
Makefile
])
During its execution I receive the following message:
./configure
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... 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 for c++... 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++... yes
checking whether c++ accepts -g... yes
checking for gawk... gawk
checking for gcc... 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... yes
checking whether gcc accepts -g... yes
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for Cygwin environment... no
checking for mingw32 environment... no
checking how to run the C preprocessor... gcc -E
checking host system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking how to recognise dependant libraries... pass_all
checking for object suffix... o
checking for executable suffix... no
checking command to parse /usr/bin/nm -B output... ok
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/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 -lc should be explicitly linked in... no
creating libtool
updating cache ./config.cache
creating ./config.status
creating test/Makefile
creating Makefile
At this point I find conftest, conftest.c and conftest.o files in my
work directory. Why are they there? How can I remove them?? am I making
a mistacke in doing what??
cheers
eli
- conftest problem using autoconf 2.13-14,
Elisabetta Ronchieri <=