jralls at ceridwen.us
Thu Dec 10 13:31:27 EST 2009
On Dec 10, 2009, at 9:25 AM, Derek Atkins wrote:
> Phil Longstaff <plongstaff at rogers.com> writes:
>>>> Why are these happening exactly ? And can they be avoided ? They make my
>>>> change-build-install-test cycle dog slow.
>>> Libtool. I don't know if there's any way to avoid them. I see them on
>>> many libtool-based applications.
>> I googled and found this:
>> Seems a few years old. Don't know why it hasn't been merged into
> Don't know, but unless we use our own version of libtool (which I would
> NOT recommend we do) then applying this patch is... problematic. I
> suppose we could modify autogen.sh to apply this patch....
That would be very hard to pull off, since different machines will have different versions of ltmain.sh. We could finesse that by having our own ltmain.sh (and other libtool scripts), but that would produce a bit of a maintenance nightmare.
Gert could apply the patch to his own ltmain.sh, but then would have to remember to re-apply it after every upgrade of libtool.
Looks like the libtool project doesn't have a public tracker, relying instead on that mailing list. Makes for an easy way to ignore bug reports.
More information about the gnucash-devel