Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: cagney@gnu.org
Cc: gdb@sources.redhat.com
Subject: Re: [proposal/testsuite] require build == host
Date: Tue, 27 Jul 2004 21:17:00 -0000	[thread overview]
Message-ID: <410679B0.nail54D11I6ZA@mindspring.com> (raw)
In-Reply-To: <4106714C.2070805@gnu.org>

ac> It would be useful, just so that we know where they are going.

I talked to Rob Savoye a month or two ago, and basically
Dejagnu is mature at this point.  I don't think it's going to
add or drop major features.

ac> For the moment, lets stick with the status quo.  Tests are required to 
ac> work host==build.  Having a test work host!=build is an added bonus, but 
ac> not a requrement.  We can hardly enforce host!=build when there's no way 
ac> to test it and the return on investment is marginal.

The machine resources are easy to get.  build == my laptop,
host == hp test drive machine (they support inbound telnet and ftp).
All I have to do is write a board file!

I'm going to move off the status quo in one direction or the other.
Either build != host is supported, or it's not.  If it is supported,
then I have to test it (sigh), and at least characterize how many tests
are broken.  If it's not supported, then I want the doco to say so.

Michael C


      parent reply	other threads:[~2004-07-27 15:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-25  1:18 Michael Chastain
2004-07-25  1:52 ` Felix Lee
2004-07-25  2:43   ` Daniel Jacobowitz
     [not found]     ` <drow@false.org>
2004-07-25 22:36       ` Felix Lee
2004-07-26 18:07         ` Michael Chastain
2004-07-27  4:41           ` Felix Lee
2004-07-25  7:59 ` Eli Zaretskii
2004-07-27  0:45 ` Andrew Cagney
2004-07-27  2:31   ` Michael Chastain
2004-07-27  4:16     ` Eli Zaretskii
2004-07-27 15:32     ` Andrew Cagney
2004-07-27 15:50       ` Christopher Faylor
2004-07-27 21:17       ` 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=410679B0.nail54D11I6ZA@mindspring.com \
    --to=mec.gnu@mindspring.com \
    --cc=cagney@gnu.org \
    --cc=gdb@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