Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Felix Lee <felix.1@canids.net>
Cc: Michael Chastain <mec.gnu@mindspring.com>, gdb@sources.redhat.com
Subject: Re: [proposal/testsuite] require build == host
Date: Sun, 25 Jul 2004 02:43:00 -0000	[thread overview]
Message-ID: <20040725015139.GA14898@nevyn.them.org> (raw)
In-Reply-To: <20040725011817.A393A1317A@grayscale.canids>

On Sat, Jul 24, 2004 at 06:18:16PM -0700, Felix Lee wrote:
> mec.gnu@mindspring.com (Michael Chastain):
> > I don't think anyone actually uses a configuration with separate build
> > and host.  So I propose this patch to document that the gdb test suite
> > requires that build and host be the same machine.
> 
> hm.  gdb runs on more systems than expect does, and my feeling at
> the moment is that it's sometimes easier to do build!=host
> testing than it is to get expect running, like on weird embedded
> linux devices.
> 
> not that I particularly like the testsuite complications added by
> build!=host, but I don't know a better alternative yet.

Have you ever actually needed to do this?

When I tested GDB on embedded Linux devices, expect was not the issue. 
Expect is easy if you have enough RAM footprint to fit a GDB binary!

Also, what is a host on which GDB works but expect does not?

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-07-25  1:52 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 [this message]
     [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

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=20040725015139.GA14898@nevyn.them.org \
    --to=drow@false.org \
    --cc=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