From: Andrew Cagney <ac131313@redhat.com>
To: DJ Delorie <dj@delorie.com>
Cc: neroden@twcny.rr.com, geoffk@apple.com,
gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: [ob] Regenerate src/configure with 000227
Date: Tue, 18 Feb 2003 21:16:00 -0000 [thread overview]
Message-ID: <3E52A3C2.90809@redhat.com> (raw)
In-Reply-To: <200302171746.h1HHkt317158@envy.delorie.com>
>> Just FYI, I've committed the attached as `obvious'. It regenerates
>> src/configure using (hopefully) the correct autoconf. Without this the
>> build barfs with the weird syntax error:
>
>
> I would argue against any autoconf *snapshot* being the "right" one.
> Aren't we supposed to be using the official fsf release of 2.13? Your
> change added the sitefile code, which wasn't there before, so it's not
> just a bugfix - it's a feature change as well.
To expand on DanielJ's comment. When fixing a GDB / BINUTILS autoconf
botch, the final patch _always_ results in the addition of the sitefile
stuff. To me, having that in the diff _is_ normal.
> Plus, you need to test this "obvious" change in the gcc tree and apply
> it there also - the trees are out of sync now, but they should be in
> sync.
Should it instead be re-generated with pure 2.13? Better first question
though is what did GeoffK use? (I'm guessing that it was Geoff's regen
that broke it).
Andrew
next prev parent reply other threads:[~2003-02-18 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 17:17 Andrew Cagney
2003-02-17 17:47 ` DJ Delorie
2003-02-17 17:50 ` Daniel Jacobowitz
2003-02-17 18:16 ` DJ Delorie
2003-02-18 21:16 ` Andrew Cagney [this message]
2003-02-18 21:23 ` DJ Delorie
2003-02-18 21:29 ` Geoffrey Keating
2003-02-19 23:33 ` Andrew Cagney
2003-02-21 1:50 ` 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=3E52A3C2.90809@redhat.com \
--to=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dj@delorie.com \
--cc=gdb-patches@sources.redhat.com \
--cc=geoffk@apple.com \
--cc=neroden@twcny.rr.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