AC_LIBOBJ doesn't exist with autoconf 2.13.
On 2002-04-03 13:17:45 +0200, Mads Martin Jørgensen wrote:
Date: Wed, 3 Apr 2002 13:17:45 +0200
From: Mads Martin Jørgensen [EMAIL PROTECTED]
To: ML mutt [EMAIL PROTECTED]
Subject: Re: Compiling problems with newer autoconf on vvv.nntp patch
* Volker Moell [EMAIL PROTECTED] [Mar 14. 2002 15:30]:
Now using the latest autoconf-2.53 I get the error message:
$ ./configure
[...]
$ make
cd . autoconf
configure.in:296: error: do not use LIBOBJS directly, use AC_LIBOBJ
(see section `AC_LIBOBJ vs. LIBOBJS' make: *** [configure] Error 1
$
The output of ./configuire seems as normal.
Any ideas? Is it a bug or did I something wrong?
--- mutt-1.3.28/configure.in.old 2002-03-13 13:49:46.0 +0100
+++ mutt-1.3.28/configure.in 2002-04-03 13:09:53.0 +0200
@@ -293,7 +293,7 @@
AC_CHECK_FUNCS(snprintf, , [mutt_cv_snprintf=yes])
AC_CHECK_FUNCS(vsnprintf, , [mutt_cv_snprintf=yes])
if test $mutt_cv_snprintf = yes; then
-LIBOBJS=$LIBOBJS snprintf.o
+ AC_LIBOBJ([snprintf])
fi
dnl SCO uses chsize() instead of ftruncate()
@@ -325,7 +325,7 @@
if test $mutt_cv_regex = yes; then
AC_DEFINE(USE_GNU_REGEX,1,[ Define if you want to use the included regex.c.
])
-LIBOBJS=$LIBOBJS regex.o
+ AC_LIBOBJ([regex])
fi
This patch fixes it.
--
Mads Martin Jørgensen, http://mmj.dk
Why make things difficult, when it is possible to make them cryptic
and totally illogic, with just a little bit more effort?
-- A. P. J.
--
Thomas Roessler [EMAIL PROTECTED] (ICQ: 127158008)
