Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] gdb-cross: Adjust ${datadir} to avoid file conflicts in sysroot
Date: Wed, 24 Apr 2013 16:15:54 +0100	[thread overview]
Message-ID: <1366816554.14512.45.camel@phil-desktop.brightsign> (raw)

GDB wants to install a bunch of files in ${datadir}/gdb/python/gdb
and ${datadir}/gdb/syscalls.  These pathnames are invariant with
TARGET_ARCH which means that if you build gdb multiple times for
different targets they will all try to write to the same location
and you get a lot of warning spew about manifest conflicts.

Prevent this by factoring the target specification into ${datadir}
so that different copies of GDB install their files into different
paths.

Signed-off-by: Phil Blundell <philb@gnu.org>
---
 meta/recipes-devtools/gdb/gdb-cross.inc |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/recipes-devtools/gdb/gdb-cross.inc b/meta/recipes-devtools/gdb/gdb-cross.inc
index 33feb58..a92d032 100644
--- a/meta/recipes-devtools/gdb/gdb-cross.inc
+++ b/meta/recipes-devtools/gdb/gdb-cross.inc
@@ -10,3 +10,5 @@ GDBPROPREFIX = ""
 
 inherit cross
 inherit gettext
+
+datadir .= "/gdb-${TUNE_PKGARCH}${TARGET_VENDOR}-${TARGET_OS}"
-- 
1.7.10.4






                 reply	other threads:[~2013-04-24 15:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1366816554.14512.45.camel@phil-desktop.brightsign \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.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