> Apart from the autoconf issues, while it's GCC policy that all changes to > the local libtool fork must have equivalents in libtool CVS first, that > means libtool CVS mainline - not 1.5 or 2.0 branches. If we move to one > of those release branches, we need to check a lot of local changes to see > whether they have equivalents on the release branch, and backport the > equivalents from mainline libtool if not. > > -- > Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/ > [EMAIL PROTECTED] (personal mail) > [EMAIL PROTECTED] (CodeSourcery mail) > [EMAIL PROTECTED] (Bugzilla assignments and CCs)
So when we finally do move to a newer libtool we will move to the unreleased libtool main line? I guess I was assuming we would move to a stable released libtool, but that was just an assumption on my part. Steve Ellcey [EMAIL PROTECTED]
