From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch] Fix parallel gdb/ make check//% site.exp
Date: Mon, 09 Nov 2009 17:50:00 -0000 [thread overview]
Message-ID: <20091109175029.GA8880@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <e394668d0911090933p1c15ffbdqbff5b23772f8aed6@mail.gmail.com>
On Mon, 09 Nov 2009 18:33:23 +0100, Doug Evans wrote:
> At Cygnus we had a general rule of keeping trees configured with relative
> paths movable, and I always forget whether we care about that anymore.
> OOC, does that impinge on this or do we no longer care about such things?
I would find it also great but in my experience it (already) does not work.
At least VPATH + srcdir are already absolute in the `gdb/testsuite.unix.*'
subdirs.
Regards,
Jan
next prev parent reply other threads:[~2009-11-09 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 12:15 Jan Kratochvil
2009-11-09 15:37 ` Tom Tromey
2009-11-09 17:20 ` Jan Kratochvil
2009-11-09 17:32 ` Tom Tromey
2009-11-09 18:00 ` Jan Kratochvil
2009-11-09 17:33 ` Doug Evans
2009-11-09 17:50 ` Jan Kratochvil [this message]
2009-11-09 17:53 ` Daniel Jacobowitz
2009-11-09 16:38 ` Doug Evans
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=20091109175029.GA8880@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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