This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Update libtool?

From: Paolo Bonzini <bonzini at gnu dot org>
To: Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>, Peter O'Gorman <peter at pogma dot com>, Jack Howarth <howarth at bromo dot msbb dot uc dot edu>, gcc at gcc dot gnu dot org
Date: Thu, 07 Aug 2008 08:53:06 +0200
Subject: Re: Update libtool?
Newsgroups: gmane.comp.gcc.devel
References: <20080805134651.GA19155@bromo.msbb.uc.edu> <48988051.1020002@pogma.com> <20080805214446.GA23703@bromo.msbb.uc.edu> <4899CE7F.1080301@pogma.com> <20080806161928.GA686@bromo.msbb.uc.edu> <4899D0A7.8040307@pogma.com> <20080806184347.GC2521@ins.uni-bonn.de>

That said, updating in trunk is a different matter.  There, the question
IMHO is mostly which libtool version to update to.  The git version may
still have a regression or two, but 2.2.4 doesn't have the -fPIC on
HP/IA patch from Steve (which would be trivial to backport of course).
Alternatively GCC can wait for 2.2.6 (hopefully in the "couple of weeks
at most" time frame).

Updating to 2.2.6 would be okay for me.

Paolo

Follow-Ups:
- Re: Update libtool?
  - From: Peter O'Gorman

References:
- libstdc++, gdb and darwin
  - From: Jack Howarth
- Re: libstdc++, gdb and darwin
  - From: Peter O'Gorman
- Re: libstdc++, gdb and darwin
  - From: Jack Howarth
- Update libtool? (was: Re: libstdc++, gdb and darwin)
  - From: Peter O'Gorman
- Re: Update libtool? (was: Re: libstdc++, gdb and darwin)
  - From: Jack Howarth
- Re: Update libtool?
  - From: Peter O'Gorman
- Re: Update libtool?
  - From: Ralf Wildenhues

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]