public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Charles Wilson <libtool@cwilson.fastmail.fm>
Cc: Steve Ellcey <sje@cup.hp.com>,
	 binutils@sourceware.org,   gcc-patches@gcc.gnu.org,
	 gdb-patches@gcc.gnu.org,   newlib@sourceware.org
Subject: Re: Patch to update libtool in GCC and Src trees
Date: Tue, 08 May 2007 06:16:00 -0000	[thread overview]
Message-ID: <46401599.7000705@lu.unisi.ch> (raw)
In-Reply-To: <463FF2AE.3000503@cwilson.fastmail.fm>


> Either way, Steve's existing patch needs to be extended to do 
> _something_ with newlib, and that means a few more days of shakedown so 
> the linux-native-newlib guys can test it.

Agreed.

> Ralf W. and I have been working on some refinements for cygwin/mingw 
> libtool in libtool's ToT over the last few weeks.  They are not yet 
> ready, and I certainly do not want to hold back gcc progress waiting on 
> libtool: the 20070318 libtool ToT included in Steve's update works fine 
> as demonstrated above.  However, now that Steve's done all or most of 
> the _hard_ work, what will be the policy going forward with regards to 
> updating external, but embedded, tools like libtool?
> 
> How often will gcc re-import the latest libtool ToT?  Any chance of 
> another -- less disruptive! -- update before 4.THREE.0 ships?

If it were only for me, we could commit to syncing libtool ToT 
periodically at least until libtool 2.0 is out.  But I suspect that to 
convince everybody, libtool would need a more precise notion of 
stable-ness.  After that, it will be the usual mess, the same as for 
Autoconf and Automake... :-)

Paolo

  reply	other threads:[~2007-05-08  6:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 18:27 Steve Ellcey
2007-05-07 20:08 ` Paolo Bonzini
2007-05-08  3:47   ` Charles Wilson
2007-05-08  6:16     ` Paolo Bonzini [this message]
2007-05-08 15:19       ` Alexandre Oliva
     [not found] <200705111829.LAA24795@hpsje.cup.hp.com>
     [not found] ` <1178917335.26350.1189384841@webmail.messagingengine.com>
     [not found]   ` <46454D61.7050509@cwilson.fastmail.fm>
     [not found]     ` <orbqgoge6k.fsf@free.oliva.athome.lsd.ic.unicamp.br>
     [not found]       ` <46494FF1.2030304@cwilson.fastmail.fm>
     [not found]         ` <464A615E.4070005@cwilson.fastmail.fm>
2007-05-16  8:03           ` Paolo Bonzini
2007-05-16 13:08             ` Charles Wilson
2007-05-16 20:39             ` Steve Ellcey
2007-05-17  5:51               ` Charles Wilson
2007-05-18 17:09             ` Steve Ellcey
2007-05-21  7:41               ` Paolo Bonzini
2007-05-21 12:12                 ` Charles Wilson
2007-05-21 13:25                   ` Paolo Bonzini
2007-05-24 14:33                 ` libtool
2007-05-24 14:34                   ` Paolo Bonzini
2007-05-24 15:38                     ` Steve Ellcey
2007-05-24 15:42                       ` Jeff Johnston
2007-05-24 15:51                         ` Steve Ellcey
2007-05-24 16:06                           ` Jeff Johnston
     [not found] <200705172103.OAA10817@hpsje.cup.hp.com>
2007-05-17 23:44 ` libtool
2007-05-18 10:06   ` Dave Korn
2007-05-18 11:16     ` Daniel Jacobowitz

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=46401599.7000705@lu.unisi.ch \
    --to=paolo.bonzini@lu.unisi.ch \
    --cc=binutils@sourceware.org \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@gcc.gnu.org \
    --cc=libtool@cwilson.fastmail.fm \
    --cc=newlib@sourceware.org \
    --cc=sje@cup.hp.com \
    /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).