From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: sje@cup.hp.com
Cc: binutils@sourceware.org, gcc-patches@gcc.gnu.org,
gdb-patches@gcc.gnu.org, newlib@sourceware.org,
Ralf.Wildenhues@gmx.de, aoliva@redhat.com,
fxcoudert@gmail.com, libtool@cwilson.fastmail.fm,
schwab@suse.de
Subject: Re: Final(?) patch to update libtool in GCC and src trees
Date: Fri, 13 Apr 2007 07:18:00 -0000 [thread overview]
Message-ID: <461F2EBD.5010700@lu.unisi.ch> (raw)
In-Reply-To: <200704101825.LAA20541@hpsje.cup.hp.com>
> OK to checkin?
I checked in the patch to fix the as/ld/nm problem on cygwin, but there
are still other issues to be solved. However, I'm sure we can first of
all limit your pain in maintaining the patch. So, if you wish, you can
checkin everything *but the new libtool* after testing on just one
platform (combined tree, or separate gcc/src builds are both okay), with
the changes I indicate below.
The patch is preapproved with those changes, but please post it again.
> Top level src tree ChangeLog:
>
> 2007-03-22 Steve Ellcey <sje@cup.hp.com>
> * src-release: Update with new libtool file list.
Obviously leave this out for now too, and keep config-ml.in in sync
between gcc and src.
> bfd/ChangeLog
> 2007-03-22 Steve Ellcey <sje@cup.hp.com>
> * configure.in: Change macro call order.
> * aclocal.m4: Regenerate.
> * Makefile.in: Regnerate.
> * configure: Regenerate.
Here, please add -I .. to Makefile.am's ACLOCAL_AMFLAGS instead of
modifying acinclude.m4.
> gas/ChangeLog
> 2007-03-22 Steve Ellcey <sje@cup.hp.com>
> * acinclude.m4: Add new includes.
> * aclocal.m4: Regenerate.
> * Makefile.in: Regenerate.
> * configure: Regenerate.
Likewise.
> gprof/ChangeLog
> 2007-03-22 Steve Ellcey <sje@cup.hp.com>
> * acinclude.m4: Add new includes.
> * aclocal.m4: Regenerate.
> * Makefile.in: Regenerate.
> * configure: Regenerate.
Likewise.
> rda/ChangeLog
> 2007-03-22 Steve Ellcey <sje@cup.hp.com>
> * acinclude.m4: Add new includes.
> * aclocal.m4: Regenerate.
> * Makefile.in: Regenerate.
> * configure: Regenerate.
Likewise.
Paolo
next prev parent reply other threads:[~2007-04-13 7:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 18:25 Steve Ellcey
2007-04-10 18:42 ` Andrew Pinski
2007-04-10 20:04 ` Steve Ellcey
2007-04-10 20:02 ` Dave Korn
2007-04-10 20:07 ` Steve Ellcey
2007-04-10 20:58 ` Dave Korn
2007-04-11 1:13 ` Dave Korn
2007-04-11 7:36 ` Paolo Bonzini
2007-04-11 8:47 ` Andreas Schwab
2007-04-11 8:51 ` Paolo Bonzini
2007-04-11 8:57 ` Ralf Wildenhues
2007-04-11 8:59 ` Paolo Bonzini
2007-04-11 9:23 ` Dave Korn
2007-04-11 9:25 ` Paolo Bonzini
2007-04-11 10:00 ` Dave Korn
2007-04-11 10:19 ` Paolo Bonzini
2007-04-11 21:41 ` Christopher Faylor
2007-04-12 10:42 ` Dave Korn
2007-04-11 2:38 ` Charles Wilson
2007-04-12 6:36 ` Charles Wilson
2007-04-12 7:03 ` Paolo Bonzini
2007-04-12 15:13 ` Steve Ellcey
2007-04-12 18:02 ` Charles Wilson
2007-04-13 7:18 ` Paolo Bonzini [this message]
2007-04-13 17:27 ` Steve Ellcey
2007-04-13 18:05 ` Daniel Jacobowitz
2007-04-13 18:18 ` Paolo Bonzini
2007-04-13 18:27 ` Steve Ellcey
2007-04-13 18:38 ` Paolo Bonzini
2007-04-13 18:44 ` Steve Ellcey
2007-04-13 20:19 ` Charles Wilson
2007-04-13 18:24 ` Paolo Bonzini
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=461F2EBD.5010700@lu.unisi.ch \
--to=paolo.bonzini@lu.unisi.ch \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@gcc.gnu.org \
--cc=libtool@cwilson.fastmail.fm \
--cc=newlib@sourceware.org \
--cc=schwab@suse.de \
--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