I've done some further looking at this problem.
On 09 Jul 2001 20:19:48 +0200, Christoph Egger wrote:
>
> On 9 Jul 2001, Thayne Harbaugh wrote:
>
> > On 09 Jul 2001 17:29:36 +0200, Christoph Egger wrote:
> > > On 9 Jul 2001, Thayne Harbaugh wrote:
> > >
> > > > ltconfig is dead with libtool 1.4 and should be removed. libtool.m4,
> > > > however, should be added. I'm putting in a patch now.
> > >
> > > I just tested your CVS changes. When I run autogen.sh I got this
> > > warning:
> > >
> > > configure.in: 42: required file `./ltconfig' not found
This is bad - apparently there is an older tool at work that is doing
this.
> >
> > I'm just not seeing this.
>
> Uhmm... I hope that you don't forget to run autogen.sh at first, when
> you are about testing your changes.
>
>
> > The only references I can find to ltconfig in the tree are in the
> > Changelog.1999. Line 42 of configure.in is an AM_PROG_LIBTOOL
> > (which is deprecated and should be AC_PROG_LIBTOOL).
> >
> > Try the following:
> >
> > grep for ltconfig in a _clean_ source tree - you shouldn't have it
> > except in Changelog.1999. This should verify that your source tree
> > doesn't have bogus files.
>
> Yep.
>
> > Check versions on libtool, automake, autoconf:
> >
> > [tharbaug@phantasm libgii]$ libtool --version
> > ltmain.sh (GNU libtool) 1.4 (1.920 2001/04/24 23:26:18)
> > [tharbaug@phantasm libgii]$ automake --version
> > automake (GNU automake) 1.4-p2
> >
> > Copyright (C) 1999, 2001 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions. There is
> > NO
> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > PURPOSE.
> >
> > Written by Tom Tromey <[EMAIL PROTECTED]>
> > [tharbaug@phantasm libgii]$ autoconf --version
> > Autoconf version 2.13
>
> I get the exact same output.
Strange. I'd expect something to be different. Somehow your configure
process is discovering AC_PROG_LIBTOOL incorrectly which then references
./ltconfig
> BTW: When I replace AM_PROG_LIBTOOL by AC_PROG_LIBTOOL as you say
> above then I don't get the
Good.
Even better try this patch:
--- configure.in.orig Mon Jul 9 15:46:34 2001
+++ configure.in Mon Jul 9 15:46:51 2001
@@ -8,7 +8,7 @@
AM_INIT_AUTOMAKE(libgii,0.7,-)
AM_MAINTAINER_MODE
-AM_DISABLE_STATIC
+AC_DISABLE_STATIC
dnl
========================================================================
dnl Set some defaults
@@ -39,7 +39,7 @@
AC_PROG_CC
AC_LIBTOOL_DLOPEN
AC_LIBTOOL_WIN32_DLL
-AM_PROG_LIBTOOL
+AC_PROG_LIBTOOL
dnl
========================================================================
> configure.in: 42: required file `./ltconfig' not found
>
> message anymore. I get this one instead:
>
> gg/Makefile.am:5: library used but `LIBTOOL' not defined in `configure.in'
>From what I understand, this isn't bad. This just says that you haven't
chosen to point "LIBTOOL" at any specific program. It should then
define this:
LIBTOOL='$(SHELL) $(top_builddir)/libtool'
$(top_builddir)/libtool is a script that should be generated during
configure. This keeps things portable rather than using a particular
libtool from a particular box.
If everything builds okay I think it's okay to ignore this warning.
> CU,
>
> Christoph Egger
> E-Mail: [EMAIL PROTECTED]
--
Thayne Harbaugh
