public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Peter O'Gorman <peter@pogma.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
	  Peter O'Gorman <peter@pogma.com>,
	 Jack Howarth <howarth@bromo.msbb.uc.edu>,
	gcc@gcc.gnu.org
Subject: Re: Update libtool?
Date: Wed, 06 Aug 2008 18:53:00 -0000	[thread overview]
Message-ID: <4899F2D3.2000107@pogma.com> (raw)
In-Reply-To: <20080806184347.GC2521@ins.uni-bonn.de>

Hi Ralf,

Ralf Wildenhues wrote:
> * Peter O'Gorman wrote on Wed, Aug 06, 2008 at 06:26:15PM CEST:
>> Jack Howarth wrote:
>>> On Wed, Aug 06, 2008 at 11:17:03AM -0500, Peter O'Gorman wrote:
>>>> I wonder what the chances are of moving mainline gcc to a newer libtool
>>>> version? Introducing the darwin bits piecemeal would not be particularly
>>>> fun.
>>>     You are going to fix this on gcc trunk in any case, right?
>> If there is a consensus that now is not the time to update libtool in
>> trunk, then I will have to :)
> 
> First off, I am not in a position to decide anything here, so the
> following is just my two cents:
> 
> I would be a bit concerned to update libtool in branch-4_3.  Is this
> issue a regression?

I have no intention of asking that libtool be updated in the 4.3 branch.

I do not consider it a regression, it has always been broken on Mac OS X
when using dwarf2.

> I haven't tried GCC trunk with libtool 2.2.4 yet, but I guess that
> should be reasonably smooth.  (Of course I'd be willing to try.)

I am also willing to try.

> 
> AFAICS there are no GCC-specific changes in these files:
> libtool.m4 ltmain.sh lt~obsolete.m4 ltoptions.m4 ltsugar.m4 ltversion.m4
> (there has been a patch to libtool.m4 but it was subsequently backed out
> again.)

Good to know. Thanks.

Peter
-- 
Peter O'Gorman
http://pogma.com

  reply	other threads:[~2008-08-06 18:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 13:50 libstdc++, gdb and darwin Jack Howarth
2008-08-05 16:32 ` Peter O'Gorman
2008-08-05 21:45   ` Jack Howarth
2008-08-06 16:18     ` Update libtool? (was: Re: libstdc++, gdb and darwin) Peter O'Gorman
2008-08-06 16:20       ` Jack Howarth
2008-08-06 16:27         ` Update libtool? Peter O'Gorman
2008-08-06 18:45           ` Ralf Wildenhues
2008-08-06 18:53             ` Peter O'Gorman [this message]
2008-08-07  6:53             ` Paolo Bonzini
2008-08-07  7:39               ` Paolo Bonzini
2008-08-07 17:29               ` Peter O'Gorman
2008-08-11 20:02                 ` Ralf Wildenhues
2008-08-11 20:03                   ` Peter O'Gorman
2008-08-21  5:36                     ` [PATCH] Update libtool to latest git tip (was: Re: Update libtool?) Peter O'Gorman
2008-08-21 14:46                       ` [PATCH] Update libtool to latest git tip Paolo Bonzini
2008-09-08 18:27                         ` Peter O'Gorman
2008-09-08 18:30                           ` Paolo Bonzini
2008-09-08 19:09                             ` Peter O'Gorman
2008-09-08 20:39                               ` Paolo Bonzini
2008-10-03 23:17   ` libstdc++, gdb and darwin Jack Howarth
2008-10-04  1:30     ` Peter O'Gorman
2008-10-04  2:26       ` Jack Howarth
2008-10-04  4:55         ` Peter O'Gorman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4899F2D3.2000107@pogma.com \
    --to=peter@pogma.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=gcc@gcc.gnu.org \
    --cc=howarth@bromo.msbb.uc.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).