Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@redhat.com>
To: Steve Ellcey <sje@cup.hp.com>
Cc: bonzini@gnu.org, libtool@cwilson.fastmail.fm,
	newlib@sourceware.org,         aoliva@redhat.com,
	gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
	        binutils@sourceware.org
Subject: Re: Patch to update libtool in GCC and Src trees
Date: Thu, 24 May 2007 15:39:00 -0000	[thread overview]
Message-ID: <4655B108.9030209@redhat.com> (raw)
In-Reply-To: <200705241515.IAA06579@hpsje.cup.hp.com>

Steve Ellcey wrote:
>> libtool@cwilson.fastmail.fm wrote:
>>     
>>> On Mon, 21 May 2007 09:40:56 +0200, "Paolo Bonzini" said:
>>>       
>>>> Ok as soon as the gcc PR32009 is solved, which should be one day or two. 
>>>>   This will also give some time to complain to the gdb/binutils/newlib 
>>>> people.
>>>>         
>>> Given
>>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32009#c9 
>>>       
>> Yes, go on.
>>
>> Paolo
>>     
>
> Just to make sure, Jeff are you OK with the newlib part of this patch?
> I think you said you were but I don't want to change the configure.in
> and Makefile.am files in newlib without being positive you are on board
> with the change too.  These changes are the ones created by Charles
> Wilson.
>
> Steve Ellcey
> sje@cup.hp.com
>   
I don't remember seeing the actual patch.  This is the one proposed that 
does not use libtool unless we ask for it so it was definitely my 
preference.  IIRC, the proposal was to change the way we set up libtool 
and it added a few macros prior to the check for libtool-used.  If that 
is correct, there should be no problem.

-- Jeff J.


  reply	other threads:[~2007-05-24 15:39 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
2007-05-16 13:08             ` Charles Wilson
2007-05-16 20:38             ` 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:26                 ` libtool
2007-05-24 14:33                   ` Paolo Bonzini
2007-05-24 15:16                     ` Steve Ellcey
2007-05-24 15:39                       ` Jeff Johnston [this message]
2007-05-24 15:42                         ` Steve Ellcey
2007-05-24 16:00                           ` 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=4655B108.9030209@redhat.com \
    --to=jjohnstn@redhat.com \
    --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