From: Doug Evans <dje@google.com>
To: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] Don't install gdb.PYTHONDIR if -nx
Date: Tue, 30 Nov 2010 18:25:00 -0000 [thread overview]
Message-ID: <AANLkTik+m_Uo2MTOOLEGqMM1rcEUnkAY50Vi9EU0VDhF@mail.gmail.com> (raw)
In-Reply-To: <20101130181904.GA29738@caradoc.them.org>
On Tue, Nov 30, 2010 at 10:19 AM, Daniel Jacobowitz
<dan@codesourcery.com> wrote:
> On Mon, Nov 29, 2010 at 09:16:33PM -0800, Doug Evans wrote:
>> On Mon, Nov 29, 2010 at 8:22 PM, Daniel Jacobowitz <dan@codesourcery.com> wrote:
>> > Why not an option to set gdb.PYTHONDIR
>> > before loading anything?
>>
>> Or rather an option to set data-directory?
>> [It might be tempting to do -x "set data-dir mumble" but -x is
>> processed too late for .gdbinit.]
>
> That would work for me. You'd need to make sure the build / testsuite
> set up something with the right layout (typical "staged install"
> problem; GCC has this issue too...).
Setting aside any system.gdbinit, that's already done: $obj/gdb/data-directory.
next prev parent reply other threads:[~2010-11-30 18:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 0:40 Doug Evans
2010-11-29 21:38 ` Tom Tromey
2010-11-30 0:03 ` [RFA, doc RFA] " Doug Evans
2010-11-30 0:30 ` Jan Kratochvil
2010-11-30 3:54 ` Eli Zaretskii
2010-11-30 4:11 ` Doug Evans
2010-11-30 11:20 ` Eli Zaretskii
2010-11-30 15:29 ` Doug Evans
2010-11-30 18:59 ` Tom Tromey
2010-12-06 20:43 ` Doug Evans
2010-12-06 20:50 ` Eli Zaretskii
2010-12-06 20:58 ` Doug Evans
2010-12-06 21:15 ` Doug Evans
2010-12-06 21:15 ` Eli Zaretskii
2010-12-06 21:16 ` Doug Evans
2010-12-06 22:17 ` Doug Evans
2010-12-07 4:02 ` Eli Zaretskii
2010-12-07 1:38 ` Jan Kratochvil
2010-11-30 4:22 ` [RFA] " Daniel Jacobowitz
2010-11-30 5:16 ` Doug Evans
2010-11-30 18:19 ` Daniel Jacobowitz
2010-11-30 18:25 ` Doug Evans [this message]
2010-11-30 5:33 ` 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=AANLkTik+m_Uo2MTOOLEGqMM1rcEUnkAY50Vi9EU0VDhF@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@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