From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Khoo Yit Phang <khooyp@cs.umd.edu>
Cc: Eli Zaretskii <eliz@gnu.org>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Warn about data-directory when failing to import Python "gdb" module
Date: Tue, 18 Sep 2012 15:44:00 -0000 [thread overview]
Message-ID: <20120918154344.GA1174@host2.jankratochvil.net> (raw)
In-Reply-To: <8A40A823-A534-4F9C-AF1A-1202E98E03B0@cs.umd.edu>
On Tue, 18 Sep 2012 17:37:40 +0200, Khoo Yit Phang wrote:
> If I understand relocate_gdb_directory, it already tries to relocate
> data-directory from /usr/local/share/gdb (GDB_DATADIR on my config) to
> build-directory/gdb/../share/gdb. Could we move the
> build-directory/gdb/data-directory there?
No.
> Otherwise, do you mean to change relocate_gdb_directory to specially check
> for GDB_DATADIR and replace it with buiid-directory/gdb/data-directory? That
> could lead to the odd possibility that an installed GDB would look for
> data-directory in a stray build directory. I suppose this can be prevented
> by checking if gdb_program_name is itself located in build-directory.
Installed GDB will have path /usr/bin/gdb and I find OK if GDB checks that
/usr/bin/data-directory/ does not exist.
Thanks,
Jan
prev parent reply other threads:[~2012-09-18 15:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 19:36 Khoo Yit Phang
2012-09-17 20:23 ` Jan Kratochvil
2012-09-17 20:28 ` Khoo Yit Phang
2012-09-17 20:36 ` Jan Kratochvil
2012-09-17 20:58 ` Joel Brobecker
2012-09-17 21:04 ` Khoo Yit Phang
2012-09-18 20:40 ` Khoo Yit Phang
2012-09-22 13:30 ` Jan Kratochvil
2012-09-22 18:37 ` Khoo Yit Phang
2012-10-06 20:56 ` Ping! " Khoo Yit Phang
2012-09-18 6:17 ` Eli Zaretskii
2012-09-18 11:58 ` Jan Kratochvil
2012-09-18 12:21 ` Eli Zaretskii
2012-09-18 13:54 ` Joel Brobecker
2012-09-18 15:38 ` Khoo Yit Phang
2012-09-18 15:44 ` Jan Kratochvil [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=20120918154344.GA1174@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=khooyp@cs.umd.edu \
/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