From: Steve Ellcey <sje@cup.hp.com>
To: drow@false.org
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: Patch to update top-level config to autoconf 2.59
Date: Thu, 10 Aug 2006 21:15:00 -0000 [thread overview]
Message-ID: <200608102102.OAA28953@hpsje.cup.hp.com> (raw)
In-Reply-To: <20060810202957.GA31776@nevyn.them.org>
> On Thu, Aug 10, 2006 at 01:08:00PM -0700, Steve Ellcey wrote:
> > Here is my final patch to update autoconf in the src tree. All subtrees
> > have been updated to be configured by autoconf 2.59 and this patch
> > updates the top level configure and Makefiles to also use 2.59. The
> > only real change needed was to rename AS_FOR_TARGET to GAS_FOR_TARGET.
> > I also changed COMPILER_AS_FOR_TARGET to COMPILER_GAS_FOR_TARGET, though
> > that wasn't strictly necessary, it just seemed like a good idea to
> > maintain the naming consistency.
>
> Why was the AS_FOR_TARGET change necessary?
Because autoconf 2.59 gave an error if I didn't change the name.
| [hpsje] $ autoconf
| configure.in:2299: error: possibly undefined macro: AS_FOR_TARGET
| If this token and others are legitimate, please use m4_pattern_allow.
| See the Autoconf documentation.
It looked like the common fix for this was to rename it to
GAS_FOR_TARGET. I see that all these files are shared, I didn't realise
that. I thought that GCC was already configuring everything with 2.59
but I see they still use 2.13 for the toplevel configure and have the
same configure.in (and Makefiles) as the src tree. Oh well.
> The top level files are all shared with GCC; you'll really have to copy
> this to gcc-patches, and I suspect they'll want you to wait until 4.2
> branches.
Yes, I expect so. I guess this last bit will have to wait for a while.
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2006-08-10 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 20:41 Steve Ellcey
2006-08-10 21:02 ` Daniel Jacobowitz
2006-08-10 21:06 ` Daniel Jacobowitz
2006-08-11 21:13 ` Christopher Faylor
2006-08-10 21:15 ` Steve Ellcey [this message]
2006-08-11 13:07 ` Daniel Jacobowitz
[not found] ` <20060810210600.GA1378__12102.1454142921$1155243979$gmane$org@nevyn.them.org>
2006-08-15 12:15 ` Paolo Bonzini
[not found] ` <44E02713.1070107__1567.96999876878$1155540766$gmane$org@lu.unisi.ch>
2006-08-15 14:25 ` Paolo Bonzini
2006-09-07 4:16 ` Ben Elliston
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=200608102102.OAA28953@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.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