> If you wait just 24 hours or so, I'll release 2.2 proper.
and that sounds like a plan! thx.
> We've tried to maintain full backwards compatibility with 1.5.x,
> ... If autoupdate doesn't migrate ... then that's a bug in the libtool
> release...
clear.
thx again!
Hello schneecrash+libtool ;-)
On 29 Feb 2008, at 14:05, snowcrash+libtool wrote:
so, as i've now seen libtool 2.x "in the wild", is it time to update
to the 2x branch?
If you wait just 24 hours or so, I'll release 2.2 proper.
how's backward compat / breakage of older,
still-using-15x stuff,
On Fri, 29 Feb 2008, snowcrash+libtool wrote:
so, as i've now seen libtool 2.x "in the wild", is it time to update
to the 2x branch? how's backward compat / breakage of older,
still-using-15x stuff, in general?
Hopefully someone will release 2.2 this weekend so that we can find
out how well
> Looks like libidn includes libtool-2.1b.
honestly, it never dawned on me to check -- 1st time i've ever come
across an app that has *newer* libtool than my self built.
> rm m4/lt* m4/libtool.m4 build-aux/ltmain.sh
> Then retry your glibtoolize autoreconf.
that did the trick! thx!
i *though
snowcrash+libtool wrote:
>
> given the above, suggestions where to look for the problem?
Looks like libidn includes libtool-2.1b.
rm m4/lt* m4/libtool.m4 build-aux/ltmain.sh
Then retry your glibtoolize autoreconf.
Peter
--
Peter O'Gorman
http://pogma.com
___
> ltmain.sh is from libtool-2.1b, aclocal.m4 has libtool.m4 from 1.5.27,
> and then later ,via m4_include, includes libtool.m4 from 2.1b. You have
> created a monster!
heh, well, ok then! :-)
i'm honestly confused though, as to what/why/how ... e.g.,
where is 2.1b coming from?
am i just luck
snowcrash+libtool wrote:
>> Now that I think about it, I would bet that the version of libtool.m4
>> that gets included in configure does not match the version of ltmail.sh
>> and does not substitute sed.
>>
>> Likely there is a libtool.m4 in acinclude.m4 or something.
>
> there is in aclocal.m4
