From: Michael Chastain <mec.gnu@mindspring.com>
To: drow@false.org
Cc: gdb-patches@sources.redhat.com, eliz@gnu.org
Subject: Re: [rfa/doco] Test Suite: build != host
Date: Thu, 19 Aug 2004 16:07:00 -0000 [thread overview]
Message-ID: <4124D03D.nail4DA118KPV@mindspring.com> (raw)
In-Reply-To: <20040819132135.GA19467@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> wrote:
> I'd just like to say... one of the few examples you had in favor of
> build != host testing was crosstool. Whoever gave you that example was
> mistaken; crosstest.sh only supports host != target, so people are
> probably -not- testing gcc with build != host.
Rats, you are right. Or, rather, cool! You are right!
I got my info from:
http://kegel.com/crosstool/current/doc/dejagnu-remote-howto.html
And somehow I got the impression that it was using --host.
Which is just plain wrong; it's all about --target_board.
> I still think this requirement is a bad idea, but it's your call.
I'm not happy either way.
I'm working towards a goal where anybody can run the doco; run the test
bed on any configuration supported in the doco; and it always works and
is useful. Like a real computer program!
One very very hard part is figuring out how to co-operate with all
the contributors and still do wrenching infrastructure upgrades.
Michael
prev parent reply other threads:[~2004-08-19 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 9:48 Michael Chastain
2004-08-19 9:56 ` Andreas Schwab
2004-08-20 15:00 ` Eli Zaretskii
2004-08-20 15:07 ` Michael Chastain
2004-08-20 16:34 ` Eli Zaretskii
2004-08-19 13:21 ` Daniel Jacobowitz
2004-08-19 16:07 ` Michael Chastain [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=4124D03D.nail4DA118KPV@mindspring.com \
--to=mec.gnu@mindspring.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.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