On Fri, Sep 08, 2000 at 04:18:48AM -0300, Alexandre Oliva wrote:
> On Sep 7, 2000, "Gary V. Vaughan" <[EMAIL PROTECTED]> wrote:
>
> > Should I commit the following to libtool as an ugly fix?
>
> > $ echo "This file is intentionally blank" > ltconfig
> > $ cvs add ltconfig
> > $ clcommit
>
> Maybe something like:
>
> #! /bin/sh
> echo "ltconfig is obsolete in this version of libtool." >&2
> exit 1
But do we really want to see loads of projects distributing this file
just because automake thinks that libtool generates it?
I am fairly strongly against having an ltconfig at all, especially
after the huge effort of getting rid of it.
> > Here is a patch to CVS automake to fix the problem properly.
>
> I don't think it fixes the problem properly. It's ok as a Quick Hack
> (TM) for us, but assumes the user is using CVS libtool, but automake
> shouldn't assume that.
Quite. I wasn't expecting it to be applied. Better that automake
checks whether libtoolize adds an ltconfig to $ac_aux_dir. But my
perl programming skills aren't up to the task.
I have added a version of this patch (generated against automake-1.4)
to the README in libtool, so that developers can patch it for
themselves if they wish to use cvs libtool. No later than when
libtool-1.4 is released, cvs automake should be patched to behave
properly with respect to having no ltconfig.
Cheers,
Gary.
--
___ _ ___ __ _ mailto: [EMAIL PROTECTED]
/ __|__ _ _ ___ _| | / / | / /_ _ _ _ __ _| |_ __ _ ___ [EMAIL PROTECTED]
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
\___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
home page: /___/ /___/ gpg public key:
http://www.oranda.demon.co.uk http://www.oranda.demon.co.uk/key.asc
