Clint Adams <[EMAIL PROTECTED]> writes:
> On Thu, Feb 14, 2008 at 04:02:41PM -0800, Russ Allbery wrote:

>> Note that libtool is an unusual case here and isn't the same as
>> Autoconf or Automake.  The files included in the package (libtool.m4
>> and ltmain.sh) are not generated files in the same sense.  Running
>> libtoolize basically just copies those files from the installed libtool
>> into the package.

> libtool.m4 is included via aclocal (unless you're not using automake),
> and then processed into configure by autoconf (unless you're not using
> autoconf).

Oh, yes, good point.  Sorry about that.

> So if you build-dep on autoconf and automake and try to use sources
> written for libtool 2.1, everything will break horribly even if you keep
> the static libtool files the same.
>
> We have been stuck with libtool 1.5 for 4 years.

I was used to upstreams that include libtool.m4 in the package, in which
case I don't believe that running aclocal will overwrite it (but maybe I'm
wrong?).  If they're pulling in libtool macros using aclocal without
keeping a local copy, that indeed will break.

-- 
Russ Allbery ([EMAIL PROTECTED])               <http://www.eyrie.org/~eagle/>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to