From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Configuring GDB with autoload directory list
Date: Sun, 09 Oct 2016 11:28:00 -0000 [thread overview]
Message-ID: <83mvidg3rh.fsf@gnu.org> (raw)
I keep around old binaries of GDB, renamed as gdb-VERSION, for testing
purposes. So I don't like it when a new installation overwrites the
data files of the old one under share/gdb/. So I configure GDB to use
a version specific directory, as in
--with-gdb-datadir=d:/usr/share/gdb/7.12
That requires me to augment the auto-load places, because those are
common, not specific to some GDB version. So I also include these two
options to configure:
--with-auto-load-dir='$debugdir;$datadir/../auto-load' --with-auto-load-safe-path='$debugdir;$datadir/../auto-load'
Note that I must use the semi-colon in these lists, because this is a
native MS-Windows build of GDB.
The problem is that this somehow doesn't work The configure script
emits the following messages:
checking for default auto-load directory... /d/gnu/gdb-7.12/gdb/configure: line 5580: \$datadir/../auto-load: No such file or directory
$debugdir;$datadir/../auto-load
checking for default auto-load safe-path... /d/gnu/gdb-7.12/gdb/configure: line 5607: \$datadir/../auto-load: No such file or directory
$debugdir;$datadir/../auto-load
and the produced gdb/config.h says just this:
/* Directories from which to load auto-loaded scripts. */
#define AUTO_LOAD_DIR "$debugdir"
/* Directories safe to hold auto-loaded files. */
#define AUTO_LOAD_SAFE_PATH "$debugdir"
What should I do to get it to say this instead:
/* Directories from which to load auto-loaded scripts. */
#define AUTO_LOAD_DIR "$debugdir;$datadir/../auto-load"
/* Directories safe to hold auto-loaded files. */
#define AUTO_LOAD_SAFE_PATH "$debugdir;$datadir/../auto-load"
? Is this a bug in GDB or am I doing something wrong?
TIA.
next reply other threads:[~2016-10-09 11:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 11:28 Eli Zaretskii [this message]
2016-10-09 11:35 ` Jan Kratochvil
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=83mvidg3rh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
/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