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: newlib@sourceware.org, Alexandre Oliva <aoliva@redhat.com>,
	  Steve Ellcey <sje@cup.hp.com>,
	 GCC Patches <gcc-patches@gcc.gnu.org>,
	 gdb-patches@sourceware.org,   binutils@sourceware.org
Subject: Re: Patch to update libtool in GCC and Src trees
Date: Wed, 16 May 2007 08:03:00 -0000	[thread overview]
Message-ID: <464ABAD4.3010409@lu.unisi.ch> (raw)
In-Reply-To: <464A615E.4070005@cwilson.fastmail.fm>


> (3) Should the configure.in's be changed to use the 'modern' libtool 
> initialization macro LT_INIT([shared static win32-dll]) -- which will 
> need to be committed simultaneously or as an integral part of Steve's 
> update; or should they instead continue to use the old 
> 'AC_LIBTOOL_WIN32_DLL; AM_PROG_LIBTOOL' macros?

I prefer to do this one step at a time, because it applies to other 
libraries too.

> (4) Once these questions are answered: Steve, do you want to 'absorb' 
> this patch into your update, so it can be committed atomically?

This would be best.  Steve, please post your patch again in reply to 
this message (I've added back binutils, gdb, and gcc mailing lists) and 
I'll ok it.

I'll look into the "standalone libtool" idea more, but this would 
already be quite a step forward.

Paolo

       reply	other threads:[~2007-05-16  8:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
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
2007-05-08 15:19       ` Alexandre Oliva

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=464ABAD4.3010409@lu.unisi.ch \
    --to=paolo.bonzini@lu.unisi.ch \
    --cc=aoliva@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.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).