I was wondering if there are any plans to move the libtool that is in
the GCC tree to 1.5? The current libtool in GCC appears to be based on
the 1.4 version and the real libtool project is currently shipping
libtool 1.5.22.
The reason I am interested in this is that I have some bugs that I
belie
On Fri, Mar 17, 2006 at 02:59:26PM -0800, Steve Ellcey wrote:
>
> I was wondering if there are any plans to move the libtool that is in
> the GCC tree to 1.5? The current libtool in GCC appears to be based on
> the 1.4 version and the real libtool project is currently shipping
> libtool 1.5.22.
> On Fri, Mar 17, 2006 at 02:59:26PM -0800, Steve Ellcey wrote:
> >
> > I was wondering if there are any plans to move the libtool that is in
> > the GCC tree to 1.5? The current libtool in GCC appears to be based on
> > the 1.4 version and the real libtool project is currently shipping
> > libto
On Mar 17, 2006, at 6:25 PM, Steve Ellcey wrote:
Or is the problem over in binutils and with combined/merged source
trees?
Combined source tree.
Plus this was just discussed this week in fact:
http://gcc.gnu.org/ml/gcc-patches/2006-03/msg00880.html
-- Pinski
On Fri, 17 Mar 2006, Steve Ellcey wrote:
> I could fix this on the 1.4 branch but I am guessing that libtool
> doesn't really want 1.4 fixes anymore and the problem is already handled
> on the 1.5 branch so I was wondering if there are plans to move GCC to
> a 1.5 libtool.
Apart from the autoconf
> 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
On Fri, 17 Mar 2006, Steve Ellcey wrote:
> 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
Yes, unless we decide to audit local changes (since libtool 2.0 branched)
for those not on libtool 2.0 branch an
Please Cc: me on replies.
* Joseph S. Myers wrote on Sat, Mar 18, 2006 at 02:10:51AM CET:
> On Fri, 17 Mar 2006, Steve Ellcey wrote:
>
> > 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
>
> Yes, unles
