Re: 278-gary-libtoolize-without-automake-or-AC_CONFIG_MACRO_DIR.diff

[Gary V. Vaughan]

Ralf Wildenhues wrote:
> Hi Gary,

Hallo Ralf,

> * Gary V. Vaughan wrote on Fri, Sep 23, 2005 at 02:17:43PM CEST:
> > For users that have an old style configure.in without AC_CONFIG_MACRO_DIR,
> > and who don't use Automake (hence no `ACLOCAL_AMFLAGS = -I m4'), libtoolize
> > currently refuses to copy any of libtool's Autoconf macros.  This changeset
> > reverts to the 1.5.x behaviour of dropping them in the current directory
> > in that case.
>
>  .. no, it doesnt, AFAICS:
>
> $ libtoolize
> | You should add the contents of `/usr/share/aclocal/libtool.m4' to
> | `aclocal.m4'.
>
> I don't think we should change this.  People should adapt to the new
> way, and since they need to make modifications anyway, they might as
> well not be hit by an update incompatibility.

That's 1.5x libtoolize you're running, no?

> Did I miss something?

No.  Here is the scenario (I'm polishing a test that does this atm):

Say I want to start to update the configury on my old non-automake
project, starting with libtool -- considering our excellent reputation
for backwards compatibility ;-)  Let's simulate that:

$ cat <<EOF >>configure.in
AC_INIT(main.c)
AC_PROG_LIBTOOL
AC_OUTPUT(Makefile)
EOF
$ touch Makefile.in main.c

Now, having installed libtool-2.0, our hypothetical upgrader does this:

$ libtoolize --version
libtoolize (GNU libtool 1.2053 2005/09/01 11:54:48) 2.1a
Written by Gary V. Vaughan <address@hidden>, 2003

Copyright (C) 2005 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.
$ autoconf
configure.in:2: error: possibly undefined macro: AC_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
$ ls
total 88
 Makefile.in      config.guess   configure      install-sh   main.c
 autom4te.cache   config.sub     configure.in   ltmain.sh
$ libtoolize --install --force
libtoolize: linking file `./config.guess'
libtoolize: linking file `./config.sub'
libtoolize: linking file `./install-sh'
libtoolize: linking file `./ltmain.sh'
$ autoconf --force
configure.in:2: error: possibly undefined macro: AC_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.

Actually, I didn't know libtool.m4 would still work by itself, which
is why I was going to drop all the macros in `.' and get the user to
add them to aclocal.m4.  You're right that the old message is cleaner.
I'll fixup the patch and repost presently.

Cheers,
        Gary.
--
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook

signature.asc
Description: OpenPGP digital signature