Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Wed, 14 Jan 2009 20:22:00 -0000	[thread overview]
Message-ID: <uhc41wsdt.fsf@gnu.org> (raw)
In-Reply-To: <20090114194922.GA13339@caradoc.them.org>

> Date: Wed, 14 Jan 2009 14:49:22 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sourceware.org, guitton@adacore.com
> 
> On Wed, Jan 14, 2009 at 09:37:55PM +0200, Eli Zaretskii wrote:
> > > The path will be automatically relocated if the GDB binary is moved,
> > > so it can be used for a system-wide directory like /etc or a
> > > prefixed directory like /opt/vendor/share.
> > 
> > Sorry, I don't understand: what does this mean?  How does one
> > ``relocate a path''?
> 
> If you configure GDB using --prefix=$prefix
> --with-system-gdbinit=$prefix/etc/gdbinit, then a GDB installed in
> $prefix/bin will load $prefix/etc/gdbinit at startup.  If the tree
> is copied to /other/prefix, then GDB will load
> /other/prefix/etc/gdbinit.

If GDB can detect the right prefix for the system-wide gdbinit file,
why does it need to be configured for a specific place ($prefix/etc)
to begin with?

> There isn't a standard name.  It's just whatever is given to the
> configure option.

Yes, I saw that much in the patch.

> Do you think it should have a standard name?

Yes, that would at least give the reader a starting point to look.

> Having --help print it out sounds wise to me.

I don't see how we can do less than that.


  reply	other threads:[~2009-01-14 20:22 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 [this message]
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
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=uhc41wsdt.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