From: Tom Tromey <tromey@redhat.com>
To: Ryan Hill <dirtyepic@gentoo.org>
Cc: gcc@gcc.gnu.org
Subject: Re: libstdc++.so.6.0.*-gdb.py might be installed at the wrong place
Date: Thu, 03 Sep 2009 20:55:00 -0000 [thread overview]
Message-ID: <m3ocpreojn.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090902230819.49f3734d@gentoo.org> (Ryan Hill's message of "Wed, 2 Sep 2009 23:08:19 -0600")
>>>>> "Ryan" == Ryan Hill <dirtyepic@gentoo.org> writes:
Ryan> I was just wondering if there was any consensus among distros
Ryan> about where to move these.
I suggest moving them either to the separate debug directory, or
underneath gdb's datadir. See (info "(gdb)Auto-loading") for details of
the procedure that gdb uses to find these files.
Tom
prev parent reply other threads:[~2009-09-03 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 20:49 Basile STARYNKEVITCH
2009-07-24 14:33 ` Ian Lance Taylor
2009-07-24 14:56 ` Basile STARYNKEVITCH
2009-07-24 15:51 ` Tom Tromey
2009-09-03 5:08 ` Ryan Hill
2009-09-03 8:51 ` Jakub Jelinek
2009-09-03 17:59 ` Ralf Wildenhues
2009-09-03 20:55 ` Tom Tromey [this message]
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=m3ocpreojn.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dirtyepic@gentoo.org \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).