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

[Gary V. Vaughan]

Hallo Ralf!

Ralf Wildenhues wrote:
> * Gary V. Vaughan wrote on Fri, Sep 23, 2005 at 03:49:34PM CEST:
> > 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:
>
> > $ 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.
>  
> Not true.  She runs aclocal and thus gets the libtool macros into
> aclocal.m4.  This is what she would've had to do with 1.5.x as well.
> So there is no such problem the way you described.

Nope, she is upgrading an autoconf/libtool project, so there is no 
aclocal program.  Probably there is a hand maintained aclocal.m4.

> > $ ls
> > total 88
> > Makefile.in      config.guess   configure      install-sh   main.c
> > autom4te.cache   config.sub     configure.in   ltmain.sh
> > $ libtoolize --install --force
>
> libtoolize 1.5.x does not know `--install'.

Our upgrader has moved to libtool-2.0.

> > 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.
>
> Yes, and please _don't_ change the libtoolize behavior.

I'm not!  I'm trying to make it behave as it did in 1.5.x.

> By the way,
> $ libtoolize-1.5
> links config.guess, config.sub, install-sh, whereas with
> $ libtoolize-2.1
> you also need --install.  Another incompatibity?

There was a huge thread on this a long time ago.  The conclusion, IIRC,
was that having libtoolize *not* compete with automake for config.guess
and friends is a feature.  There was also some fuss about install-sh,
which I don't remember exactly, except that I disagreed with it ;-)

> So: if you want to copy libtool.m4, educate users to use
> AC_CONFIG_MACRO_DIR, and if only with [.] as argument.

No I don't want to do anything new; just have libtoolize tell the user
how to continue.  Pointing them at $prefix/shared/libtool/m4/libtool.m4
is more than adequate, and the same as the 1.5.x behaviour too.

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