On Fri, 11 May 2007 18:14:48 -0400, "Jeff Johnston"
My question is how volatile is libtool going to be? I'm getting kind of
tired of having to change newlib whenever autoconf/automake decides to
change something. If libtool is simply going to continue working
without constant changes, then Chuck's option 2 seems to make the most
sense, though a bit tedious.
I don't really understand this: "whenever autoconf/automake decides to
change something." The src- tree has standardized on specific versions
of autoconf and automake: 2.59 and 1.9.6, respectively. Those are
released versions: they don't "change". Current autoconf "changes" are
happening in autoconf-2.61+, and current automake "changes" are
happening in automake-1.10.+. How do those changes affect newlib, which
is (supposedly) using the carved-in-stone 2.59/1.9.6 releases?
Now, maybe you're reacting to all the upheaval in the past two years in
which the src- and gcc- trees were laboriously converted TO 2.59/1.9.6.
But that's all done now (pace' Steve's current libtool work). And once
Steve's libtool-20070318 stuff is imported...I expect future changes to
be relatively rare (although I doubt you'll get away with *five years*
between libtool updates anymore!). This 'relative rarity' will
probably prove unfortunate for me -- as I mentioned earlier I'm
currently working on some cygwin/mingw libtool improvements, but if I've
'missed the window', then they will just have to wait 'til libtool-2.x.
'sokay.