From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] Fix completion.exp on relative srcdir path
Date: Thu, 10 Jan 2002 18:42:00 -0000 [thread overview]
Message-ID: <npd70hsj3d.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: Daniel Jacobowitz's message of Wed, 9 Jan 2002 20:40:06 -0500
Daniel Jacobowitz <drow@mvista.com> writes:
> I always configure with relative paths - srcdir = ../../../src/gdb/testsuite
> or so. That caused a bogus failure. Is this patch OK?
What's behind the `cd ${objdir}' there that you're not doing anything
with? Is the patch incomplete, or does it need to be cleaned up?
If you address that, and add a comment explaining why what you're
doing is necessary, then this patch looks good.
>
> --
> Daniel Jacobowitz Carnegie Mellon University
> MontaVista Software Debian GNU/Linux Developer
>
> 2002-01-09 Daniel Jacobowitz <drow@mvista.com>
>
> * gdb.base/completion.exp: Expand ${srcdir} to an absolute path.
>
> Index: completion.exp
> ===================================================================
> RCS file: /cvs/src/src/gdb/testsuite/gdb.base/completion.exp,v
> retrieving revision 1.10
> diff -u -p -r1.10 completion.exp
> --- completion.exp 2001/12/17 22:58:42 1.10
> +++ completion.exp 2002/01/10 01:37:15
> @@ -656,8 +656,13 @@ gdb_expect {
> timeout { fail "(timeout) complete 'file ./Make'" }
> }
>
> +set mydir [pwd]
> +cd ${objdir}
> +cd ${srcdir}
> +set fullsrcdir [pwd]
> +cd ${mydir}
>
> -gdb_test "cd ${srcdir}" "Working directory ${srcdir}.*" "cd to \${srcdir}"
> +gdb_test "cd ${fullsrcdir}" "Working directory ${fullsrcdir}.*" "cd to \${srcdir}"
> send_gdb "file ./gdb.base/compl\t"
> sleep 1
> gdb_expect {
>
next prev parent reply other threads:[~2002-01-11 2:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 17:39 Daniel Jacobowitz
2002-01-10 18:42 ` Jim Blandy [this message]
2002-01-10 18:49 ` Daniel Jacobowitz
2002-01-13 14:13 ` 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=npd70hsj3d.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=drow@mvista.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