From: Daniel Jacobowitz <drow@false.org>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: add check// targets to gdb
Date: Mon, 07 Jun 2004 15:23:00 -0000 [thread overview]
Message-ID: <20040607152323.GB17470@nevyn.them.org> (raw)
In-Reply-To: <orfz9crimn.fsf@livre.redhat.lsd.ic.unicamp.br>
On Thu, Jun 03, 2004 at 08:22:24AM -0300, Alexandre Oliva wrote:
> On Jun 3, 2004, Alexandre Oliva <aoliva@redhat.com> wrote:
>
> > BTW, I just found out the patch didn't quite work. There are some
> > sub-subdirectories of testsuite that have to be configured as well.
> > I'll post an update later.
Configure can be run in the testsuite directory directly; I do this
when testing an installed GDB. I think that would be substantially
simpler than the search for config.status, which may blow up (for
instance) when a directory is removed...
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-06-07 15:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 2:31 Alexandre Oliva
2004-06-03 3:17 ` Daniel Jacobowitz
2004-06-03 6:08 ` Alexandre Oliva
2004-06-03 11:22 ` Alexandre Oliva
2004-06-07 15:23 ` Daniel Jacobowitz [this message]
2004-06-07 20:08 ` Alexandre Oliva
2004-06-07 20:11 ` Daniel Jacobowitz
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=20040607152323.GB17470@nevyn.them.org \
--to=drow@false.org \
--cc=aoliva@redhat.com \
--cc=gdb-patches@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