From: Ralf Corsepius <ralf.corsepius@rtems.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: status on gdb-7.4 release...
Date: Thu, 22 Dec 2011 09:33:00 -0000 [thread overview]
Message-ID: <4EF2EC52.4050300@rtems.org> (raw)
In-Reply-To: <20111222081119.GR23376@adacore.com>
On 12/22/2011 09:11 AM, Joel Brobecker wrote:
>> OK, then ... wouldn't it be better to install this header into a
>> versioned directory, say
>>
>> $(includedir)/gdb-$(GDB_VERSION)
>> or
>> $(includedir)/gdb/$(GDB_VERSION)
>> ?
>>
>> Otherwise this file will conflict with other gdbs' versions of this
>> file when having different versions of gdb installed in parallel[1]
>> and should this file change in future versions of gdb.
> The same is true of everything else that goes into the so-called
> gdb-datadir, I think.
Agreed.
> What we should probably do is make the default
> gdb-datadir versioned. This is in fact what we manually do at AdaCore,
> by configuring with --with-gdb-datadir.
I so far have been using --with-gdb-datadir=$(datadir)/$(target)-gdb
Likely you are right and I should start using a versioned directory.
> But if this is something you'd like to pursue, it'd be better if
> you did so in a separate thread. I'd like to keep this purely to
> track the release. And the suggestion above have drawbacks, so
> it's not a no-brainer.
>
Agreed. I'll try to use a versioned --includedir and --with-gdb-datadir
in my next build spin.
Ralf
next prev parent reply other threads:[~2011-12-22 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 7:09 Joel Brobecker
2011-12-22 7:25 ` Ralf Corsepius
2011-12-22 7:59 ` Joel Brobecker
2011-12-22 8:05 ` Ralf Corsepius
2011-12-22 8:41 ` Joel Brobecker
2011-12-22 9:33 ` Ralf Corsepius [this message]
2011-12-22 10:03 ` Jan Kratochvil
2011-12-22 10:13 ` Andreas Schwab
2011-12-22 10:21 ` Joel Brobecker
2011-12-22 10:35 ` Mark Kettenis
2011-12-22 17:07 ` Tom Tromey
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=4EF2EC52.4050300@rtems.org \
--to=ralf.corsepius@rtems.org \
--cc=brobecker@adacore.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