From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] print '--with{,out}-babeltrace' in 'gdb --configuration'
Date: Thu, 18 Apr 2013 04:32:00 -0000 [thread overview]
Message-ID: <CADPb22RcDd7LyyTL=TWpkxFS+s6hx+_xRL-_+iiWgZG0qRu=VA@mail.gmail.com> (raw)
In-Reply-To: <83obdd2irl.fsf@gnu.org>
On Wed, Apr 17, 2013 at 10:01 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 17 Apr 2013 10:54:10 +0800
>> From: Yao Qi <yao@codesourcery.com>
>> CC: Eli Zaretskii <eliz@gnu.org>, gdb-patches <gdb-patches@sourceware.org>
>>
>> The "relocatable" is unclear to me unless I checked configure.ac and
>> previous discussions.
>
> I will add something to explain that, assuming I will find a way to
> say that concisely.
[for completeness sake]
I'd be ok with just adding something to the manual.
It would be good to document the fact that a gdb install tree can be
moved and gdb will still find its relocatable ancillary files.
This goes along with the ability to do "make install DESTDIR=/foo"
which is a nice capability.
next prev parent reply other threads:[~2013-04-17 17:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 14:48 Yao Qi
2013-04-12 15:45 ` Eli Zaretskii
2013-04-17 11:02 ` Yao Qi
2013-04-16 1:56 ` Doug Evans
2013-04-16 10:11 ` Eli Zaretskii
2013-04-17 7:40 ` Doug Evans
2013-04-17 9:40 ` Yao Qi
2013-04-17 10:02 ` Doug Evans
2013-04-17 12:54 ` Yao Qi
2013-04-17 22:44 ` Eli Zaretskii
2013-04-18 4:32 ` Doug Evans [this message]
2013-06-22 20:03 ` Eli Zaretskii
2013-06-22 22:21 ` Sergio Durigan Junior
2013-06-23 2:21 ` Eli Zaretskii
2013-06-23 2:23 ` Sergio Durigan Junior
2013-06-24 18:43 ` Doug Evans
2013-06-24 19:03 ` Eli Zaretskii
2013-06-24 19:04 ` Doug Evans
2013-06-24 19:28 ` Eli Zaretskii
2013-06-24 19:33 ` Doug Evans
2013-07-06 7:36 ` Eli Zaretskii
2013-04-17 14:21 ` Eli Zaretskii
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='CADPb22RcDd7LyyTL=TWpkxFS+s6hx+_xRL-_+iiWgZG0qRu=VA@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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