chicken-users
[Top][All Lists]
Advanced

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

[Chicken-users] autocvs, configure, etc


From: Peter Keller
Subject: [Chicken-users] autocvs, configure, etc
Date: Sun, 29 Sep 2002 23:28:05 -0500
User-agent: Mutt/1.2i

Hello,

I upgraded autoconf and libtool to 2.54 and 1.4.2 respectively
cause I needed some features and bug fixes for things I've been
writing. Unfortunately, I sorta noticed too late that autoconf 2.54 is
vastly different and _nearly_ compatible with autoconf 2.13, which seems
to be the last stable release before the 2.50 jump happened.

Now, when I run autocvs in the chicken sources I get this:
Linux black > ./autocvs
WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
WARNING: and `config.h.top', to define templates for `config.h.in'
WARNING: is deprecated and discouraged.

WARNING: Using the third argument of `AC_DEFINE' and
WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
WARNING: `acconfig.h':

WARNING:   AC_DEFINE([NEED_MAIN], 1,
WARNING:             [Define if a function `main' is needed.])

WARNING: More sophisticated templates can also be produced, see the
WARNING: documentation.
autoheader: `config.h.in' is unchanged
Linux black > 

And then when I run configure, I get this:

Linux black > ./configure
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 build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-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 for gcc option to accept ANSI C... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking for ranlib... ranlib
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
ltconfig: you must specify a host type if you use `--no-verify'
Try `ltconfig --help' for more information.
configure: error: libtool configure failed
Linux black > 

Is it possible to update the chicken autoconf stuff so it can work with
autoconf 2.5 and 2.13?

I barely know autoconf so far(though I'm learning it slowly) so I don't
think I'm able to do this update of the sources without subtracting lots
of time from the other things I'm working on currently, and I sorta want
to see those other things working cause they are close to being done. :)

Thanks.

-pete




reply via email to

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