[OE-core] [PATCH v3 2/8] gdb-cross: avoid tune specific paths

[Mark Hatle]

On 4/11/17 9:56 AM, Patrick Ohly wrote:
> 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.

Are you sure about this.  On non-intel architectures, it used to be VERY common
that the specific instruction set for a process was programmed into gdb.

Sometimes the user could (after loading gdb) change the instructions, but this
was an aweful user experience.

Good example of this would be Power, e500, etc.  The instruction sets are not
actually compatible with each other, so GDB needs to know the specific
instruction in order to work.

--Mark

> 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.
> 
> Signed-off-by: Patrick Ohly <patrick.ohly at intel.com>
> ---
>  meta/recipes-devtools/gdb/gdb-cross.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-devtools/gdb/gdb-cross.inc b/meta/recipes-devtools/gdb/gdb-cross.inc
> index a34223e..d92f31f 100644
> --- a/meta/recipes-devtools/gdb/gdb-cross.inc
> +++ b/meta/recipes-devtools/gdb/gdb-cross.inc
> @@ -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}"
>