public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Steve Ellcey <sje@cup.hp.com>
To: gcc-patches@gcc.gnu.org, binutils@gcc.gnu.org, 	gdb-patches@gcc.gnu.org
Subject: Re: Patch to update libtool in GCC and binutils trees
Date: Fri, 23 Mar 2007 16:22:00 -0000	[thread overview]
Message-ID: <4603FE9F.1050708@cup.hp.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 353 bytes --]

This is a follow up patch with the libtool changes for the top-level of 
the GCC and binutils tree.  My first attempt to send this bounced 
because the patch was too big.  Here is is as a compressed attachment. 
The patch does not delete ltconfig, ltcf-c.sh, ltcf-cxx.sh, and 
ltcf-gcj.sh.  That needs to be done by hand.

Steve Ellcey
sje@cup.hp.com



[-- Attachment #2: Top --]
[-- Type: text/plain, Size: 352 bytes --]

2007-03-22  Steve Ellcey  <sje@cup.hp.com>
	* ltmain.sh: Update from ToT Libtool.
	* libtool.m4: Update from ToT Libtool.
	* ltsugar.m4: New. Update from ToT Libtool.
	* ltversion.m4: New. Update from ToT Libtool.
	* ltoptions.m4: New. Update from ToT Libtool.
	* ltconfig: Remove.
	* ltcf-c.sh: Remove.
	* ltcf-cxx.sh: Remove.
	* ltcf-gcj.sh: Remove.

[-- Attachment #3: libtool.diff.gz --]
[-- Type: application/x-gzip, Size: 162357 bytes --]

             reply	other threads:[~2007-03-23 16:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-23 16:22 Steve Ellcey [this message]
2007-03-26 16:47 ` Steve Ellcey
2007-03-26 18:04   ` Paolo Bonzini
  -- strict thread matches above, loose matches on Subject: below --
2007-03-23  7:29 Paolo Bonzini
     [not found] ` <200703231550.IAA20980@hpsje.cup.hp.com>
2007-03-23 16:12   ` François-Xavier Coudert
2007-03-22 22:56 FX Coudert
2007-03-22 21:27 Steve Ellcey

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=4603FE9F.1050708@cup.hp.com \
    --to=sje@cup.hp.com \
    --cc=binutils@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@gcc.gnu.org \
    /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).