From: Phil Edwards <phil@jaj.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Nathanael Nerode <neroden@twcny.rr.com>,
gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: (toplevel patch) Use canonical names for target_subdir, build_subdir.
Date: Sat, 25 Jan 2003 21:27:00 -0000 [thread overview]
Message-ID: <20030125212716.GA28741@disaster.jaj.com> (raw)
In-Reply-To: <m3wukudp4i.fsf@whitebox.local>
On Sat, Jan 25, 2003 at 01:55:41AM +0100, Andreas Schwab wrote:
> Nathanael Nerode <neroden@twcny.rr.com> writes:
>
> > Use the canonical build and target names for build_subdir and target_subdir.
> > This saves a tedious amount of work when we get around to autoconf 2.5x
> > conversion (where build_alias and target_alias may be empty strings).
> >
> > Built successfully on i686-pc-linux-gnu. (But then, this should make no
> > difference at all in the native case.)
>
> Did you try "make check"? It's currently completely broken, see
> gcc-testresults.
Indeed. I build on athlon_mp-pc-linux-gnu, and the target subdir just
moved out from underneath me...
(On the plus side, the toplevel configury is human-readable these days. :-)
So it was easy to find and revert locally. Thanks again for doing all that.)
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
prev parent reply other threads:[~2003-01-25 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 3:41 Nathanael Nerode
2003-01-24 16:51 ` Alexandre Oliva
2003-01-24 18:32 ` Nathanael Nerode
2003-01-24 19:16 ` Alexandre Oliva
2003-01-26 12:22 ` Phil Edwards
2003-01-26 12:45 ` Alexandre Oliva
2003-01-27 14:56 ` Phil Edwards
2003-01-27 15:26 ` Phil Edwards
2003-01-25 0:56 ` Andreas Schwab
2003-01-25 21:27 ` Phil Edwards [this message]
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=20030125212716.GA28741@disaster.jaj.com \
--to=phil@jaj.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.com \
--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