Re: autoheader problem

[Tim Van Holder]

On 13 Jun 2001 17:23:11 -0400, Bobby Wintemberg wrote:
> Hello,
> 
> AC_INIT(acinclude.m4)
We may need to see this file as well (it'll probably contain
kdevelop's own support macros, which may have further
compatibility problems with autoconf 2.50).

> dnl checks for programs.
> dnl first check for c compiler
> AC_CHECK_C_COMPILER

This might be a problem, but that depends on how this macro
is defined (it's probably in acinclude.m4).

> dnl create a working libtool-script
> if test -z "$LIBTOOL"; then
>   AC_LANG_SAVE
>   AC_LANG_C
These are probably the culprit; I think the language macros
use a different syntax in 2.50.

>   AC_LIBTOOL_DLOPEN
>   AM_PROG_LIBTOOL
>   dnl LIBTOOL="$LIBTOOL --silent"
>   dnl AC_SUBST(LIBTOOL)
>   AC_LANG_RESTORE
>   LIBTOOL_SHELL='/bin/sh ./libtool'
> else
>   LIBTOOL_SHELL=$LIBTOOL
> fi
> 
> dnl check for presence of dynamic-loading-library functions
> KDE_CHECK_LIBDL

This whole things seems fishy; why aren't they simply using
AC_PROG_LIBTOOL?  Isn't that the canonical way to use libtool?

At the very least you should log a bug report with the kdevelop
team to say the configure.ins they generate aren't compatible with
autoconf 2.50.
I'm sure Akim will be able to quickly point out what you need to
change in configure.in to make it work;  I just hope kdevelop won't
screw it up again after that.

-- 
Tim Van Holder - Anubex N.V.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
This message was posted using plain text. I do not endorse any
products or services that may be hyperlinked to this message.