gdb-cross: avoid tune specific paths

gdb-cross used to be specific to the tune flags, but isn't
anymore. Therefore it is enough to use TARGET_SYS instead of
TUNE_PKGARCH to create a unique path.

Fixes a sstate signature difference that was found via
yocto-compat-layer.py's test_machine_signatures check. In practice it
probably showed up as unnecessarily rebuilding gdb-cross when
switching between machines like intel-corei7-64 and qemux86-64.

(From OE-Core rev: f346473a4868563db7fb63665e808c3fe25a8b58)

Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Patrick Ohly 2017-04-11 20:38:37 +02:00 committed by Richard Purdie
parent 30686e2fd6
commit fc43f10a51
1 changed files with 1 additions and 1 deletions

View File

@ -24,4 +24,4 @@ BPN = "gdb"
inherit cross
inherit gettext
datadir .= "/gdb-${TUNE_PKGARCH}${TARGET_VENDOR}-${TARGET_OS}"
datadir .= "/gdb-${TARGET_SYS}${TARGET_VENDOR}-${TARGET_OS}"