On 9 Jul 2001, Thayne Harbaugh wrote:
> > 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
> ========================================================================
This change has no visual effect for me. I still get the warning
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'
Yes. I found this in configure.
> $(top_builddir)/libtool is a script that should be generated during
> configure.
Yep. It is created.
> 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.
This is the case for me.
Great work, Thayne. Keep it!
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
