public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Jimmy Guo <guo@cup.hp.com>
Cc: gdb@sourceware.cygnus.com,
	"Insight (GDB GUI)" <insight@sourceware.cygnus.com>
Subject: Re: gdb.gdbtk tests
Date: Thu, 23 Mar 2000 16:50:00 -0000	[thread overview]
Message-ID: <38DABB2B.4132769A@cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10003231557490.9146-100000@hpcll168.cup.hp.com>

Jimmy Guo wrote:
> 
> >They are already available.  Either download the insight+dejagnu
> >snapshot or checkout the module ``insight''.
> 
> Oh, I only extract gdb + dejagnu.
> 
> >The ``GDB'' module doesn't include the gdb.gdbtk testsuites.  However,
> >given that it's pretty easy to end up with that directory, a more robust
> >test would be better.
> 
> I don't know if there's any easy way to maintain the modules aliases to
> separate out the gdb.gdbtk test suite from mainline gdb tree.  As of
> 3/21 that's not the case (or I wouldn't see the test suite).  Keeping it
> in the tree would be fine provided that a better bypass than the current
> (let TCL complain about 'cd' failure and dump call trace).  For now,
> locally, I'm adding gdb.gdbtk to the skip list in site.exp.

At a technical level, yes it is possible.  The modules file and the
repository can be structured such that ``cvs co'' mix-n-matches a
collection of directories into a specific local structure. It was
considered when the GDB and binutils repositories were merged but
discarded as unnecessary at the time.

The relevant tests should be fixed.

	Andrew

      reply	other threads:[~2000-03-23 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10003231245280.9146-100000@hpcll168.cup.hp.com>
2000-03-23 14:56 ` Andrew Cagney
2000-03-23 15:02   ` Jimmy Guo
2000-03-23 16:50     ` Andrew Cagney [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=38DABB2B.4132769A@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=guo@cup.hp.com \
    --cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).