From: Joel Brobecker <brobecker@adacore.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org, Masaki Muranaka <monaka@monami-software.com>
Subject: Re: [doc] Avoid conflicts between gdb and cross-gdb.
Date: Wed, 06 Aug 2014 13:24:00 -0000 [thread overview]
Message-ID: <20140806132435.GC5204@adacore.com> (raw)
In-Reply-To: <3531941.zJjkhARRvn@vapier>
> along these lines, should we also transform the default gdb datadir (for
> python and xml files) ? and info pages ? looking at my cross-debugger
> installs, those are the other big missing pieces.
For the default gdb_datadir, I am of two minds on this. It's really
easy to adjust as desired at configure time, and I think that multiple
GDB installs made at the same location should be compatible, and
thus should be able to share their Python/XML files. But as previously
said, it's not a strong opinion.
For GDB's info page, I think we should indeed apply the transformation,
to be consistent.
--
Joel
next prev parent reply other threads:[~2014-08-06 13:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 8:18 Masaki Muranaka
2014-08-01 15:07 ` Joel Brobecker
2014-08-02 12:58 ` Mike Frysinger
2014-08-06 13:24 ` Joel Brobecker [this message]
2014-08-06 17:05 ` Eli Zaretskii
2014-08-06 17:37 ` Joel Brobecker
2014-08-06 17:40 ` Eli Zaretskii
2014-08-06 19:53 ` Joel Brobecker
2014-08-06 20:05 ` Doug Evans
2014-08-06 21:34 ` Joel Brobecker
2014-08-07 15:43 ` Eli Zaretskii
2014-08-07 15:53 ` Joel Brobecker
2014-08-08 6:19 ` Mike Frysinger
2014-08-21 14:26 ` Pedro Alves
2014-08-21 15:00 ` Eli Zaretskii
2014-08-07 0:21 ` Mike Frysinger
2014-08-07 15:50 ` Eli Zaretskii
2014-08-08 2:53 ` Mike Frysinger
2014-08-08 6:05 ` Eli Zaretskii
2014-08-08 7:17 ` Mike Frysinger
2014-08-21 14:30 ` Pedro Alves
2014-08-06 22:55 ` Mike Frysinger
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=20140806132435.GC5204@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=monaka@monami-software.com \
--cc=vapier@gentoo.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