From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org, guitton@adacore.com
Subject: Re: Add support for --with-system-gdbinit
Date: Thu, 15 Jan 2009 04:10:00 -0000 [thread overview]
Message-ID: <ud4epw6pi.fsf@gnu.org> (raw)
In-Reply-To: <20090114230629.GA8400@caradoc.them.org>
> Date: Wed, 14 Jan 2009 18:06:29 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sourceware.org, guitton@adacore.com
>
> I understand now. There's an alternative to keeping it in the same
> tree:
>
> --prefix=/my/working/directory --with-system-gdbinit=/etc/gdbinit
>
> In this version /etc is not relative to $prefix, so it wasn't
> redundant. This example may seem a little weird, but it makes more
> sense for --with-debug-file-directory; your native system's libraries
> are always in /usr/lib/debug, no matter where GDB goes.
Thanks for explaining this. Now I'm quite sure this needs to be
explained in the manual somewhere, or maybe in INSTALL.
next prev parent reply other threads:[~2009-01-15 4:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 13:56 Daniel Jacobowitz
2009-01-14 19:39 ` Eli Zaretskii
2009-01-14 19:50 ` Daniel Jacobowitz
2009-01-14 20:22 ` Eli Zaretskii
2009-01-14 20:38 ` Daniel Jacobowitz
2009-01-14 21:55 ` Eli Zaretskii
2009-01-14 23:07 ` Daniel Jacobowitz
2009-01-15 4:10 ` Eli Zaretskii [this message]
2009-01-19 14:11 ` Jerome Guitton
2009-01-19 14:20 ` Daniel Jacobowitz
2009-01-19 18:40 ` Eli Zaretskii
2009-01-21 10:54 ` Jerome Guitton
2009-01-21 19:03 ` Eli Zaretskii
2009-01-23 17:24 ` Jerome Guitton
2009-01-23 22:55 ` Eli Zaretskii
2009-01-28 18:00 ` Jerome Guitton
2009-01-23 17:42 ` Daniel Jacobowitz
2009-01-26 9:12 ` Jerome Guitton
2009-01-26 14:59 ` Daniel Jacobowitz
2009-01-28 15:06 ` Jerome Guitton
2009-01-16 11:54 ` Jerome Guitton
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=ud4epw6pi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.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