From: Felix Lee <felix.1@canids.net>
To: Michael Chastain <mec.gnu@mindspring.com>, gdb@sources.redhat.com
Subject: Re: [proposal/testsuite] require build == host
Date: Sun, 25 Jul 2004 22:36:00 -0000 [thread overview]
Message-ID: <20040725074042.2F25A131B5@grayscale.canids> (raw)
In-Reply-To: <20040725015139.GA14898@nevyn.them.org> on Sat, 24 Jul 2004 21:51:39 EDT from Daniel Jacobowitz <drow@false.org>
Daniel Jacobowitz <drow@false.org>:
> Also, what is a host on which GDB works but expect does not?
I remember running build!=host tests in some situations, but I
don't remember enough detail to demonstrate that it was really
necessary. at the moment I'm mostly using retrograde reasoning:
the build!=host machinery is nontrivial, and it seems unlikely
that people would go to all that trouble if it were easy to just
get build==host working.
the issue isn't memory footprint, it's stuff like OS environment.
one thing that comes to mind: expect won't work if you don't have
ptys, but gdb works fine without ptys. also, BeOS apparently has
a weird select() call that's hard to work with.
I think most of the build!=host machinery was invented in the
early days of cygwin testing. it isn't necessary for cygwin now,
but it might be needed elsewhere.
--
next prev parent reply other threads:[~2004-07-25 7:59 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 [this message]
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
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=20040725074042.2F25A131B5@grayscale.canids \
--to=felix.1@canids.net \
--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