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

> ac> What do the dejagnu maintainers have to say about the feature?
> 
> I haven't asked, but it's a supported feature of dejagnu and I'm
> willing to accept that they will keep on supporting it.

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

> Dan Kegel is at least one user of dejagnu who uses build != host
> with gcc.  He wrote a whole section in his cross-gcc faq about it.
> People are testing gcc with dejagnu using build != host,
> so it would be good if gdb testing worked in the same environment.
> 
> ac> As for a system that would/should use this - djgpp.
> 
> You got me there.  It's been a while since I used windows,
> but I suspect that windows has telnet/ftp servers.
> 
> Eli, is it possible to ftp into a windows box and upload and
> download files?  More important, is it possible to telnet into
> a windows box and run a command-line interpreter?

This is how the original cygwin testing was done - at a dos prompt.

> It looks like I should go with Plan B: file PR's against the
> test scripts that don't work on build != host, and eventually
> fix them.

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

Andrew




  parent reply	other threads:[~2004-07-27 15:14 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 [this message]
2004-07-27 15:50       ` Christopher Faylor
2004-07-27 21:17       ` Michael Chastain

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=4106714C.2070805@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=mec.gnu@mindspring.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