Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Steve Ellcey <sje@cup.hp.com>
To: bonzini@gnu.org
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 17:27:00 -0000	[thread overview]
Message-ID: <200704131707.KAA20364@hpsje.cup.hp.com> (raw)
In-Reply-To: <461F2EBD.5010700@lu.unisi.ch>

> The patch is preapproved with those changes, but please post it again.

Just to be clear, this approval is for both the GCC and the Src tree
right?

> > 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.

OK, If the config-ml.in change works with the old libtool I will make
the change in both trees.  Otherwise I will leave them both alone.

> > 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.

That seems like a good idea.  I did the change with sinclude because the
src tree seemed to use sinclude's instead of ACLOCAL_AMFLAGS.  If I am
adding ACLOCAL_AMFLAGS should I add -I ../config and -I ../bfd too and
remove all the sinclude statements from the acinclude.m4 scripts?

My plan is to make the changes you want, test with the new libtool to
make sure that works, then revert to the old libtool, retest, and check
in the changes when that works.  It may take a few days.

Steve Ellcey
sje@cup.hp.com


  reply	other threads:[~2007-04-13 17:07 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
2007-04-13 17:27   ` Steve Ellcey [this message]
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=200704131707.KAA20364@hpsje.cup.hp.com \
    --to=sje@cup.hp.com \
    --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 \
    /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