mirror of
https://git.yoctoproject.org/poky
synced 2026-02-20 08:29:42 +01:00
3e903cb42f
"yocto-compat-layer.py --machines" showed that shared packages like gcc-cross-powerpc64 have a sstate signature that depends on TUNEFLAGS. As a result, there are unnecessary rebuilds and potential conflicts in a multiconfig. That's due to the way how TARGET_ARCH is set. Richard Purdie suggested setting TARGET_ARCH[vardepvalue] as fix, which works. It would be shorter to do that in cross.bbclass instead of repeating the relevant line in different recipes, but Richard was concerned about potential side-effects in other usages of cross.bbclass. TARGET_GOARM as used in go.inc is still causing signature differences for go-cross-powerpc64 and machines b4420qds-64b and p5020ds-64b. This needs further investigation. (From OE-Core rev: 39bfa0dd3237cbca47e7fca1075d521f9d073f25) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
31 lines
797 B
PHP
31 lines
797 B
PHP
require gdb-common.inc
|
|
|
|
DEPENDS = "expat-native ncurses-native flex-native bison-native"
|
|
|
|
inherit python3native
|
|
|
|
# Overrides PACKAGECONFIG variables in gdb-common.inc
|
|
PACKAGECONFIG ??= "python readline"
|
|
PACKAGECONFIG[python] = "--with-python=${PYTHON},--without-python,python3-native"
|
|
PACKAGECONFIG[readline] = "--with-system-readline,--without-system-readline,readline-native"
|
|
|
|
do_compile_prepend() {
|
|
export STAGING_LIBDIR="${STAGING_LIBDIR_NATIVE}"
|
|
export STAGING_INCDIR="${STAGING_INCDIR_NATIVE}"
|
|
}
|
|
|
|
#EXTRA_OEMAKE += "LDFLAGS='${BUILD_LDFLAGS}'"
|
|
|
|
GDBPROPREFIX = ""
|
|
|
|
PN = "gdb-cross-${TARGET_ARCH}"
|
|
BPN = "gdb"
|
|
|
|
# Ignore how TARGET_ARCH is computed.
|
|
TARGET_ARCH[vardepvalue] = "${TARGET_ARCH}"
|
|
|
|
inherit cross
|
|
inherit gettext
|
|
|
|
datadir .= "/gdb-${TARGET_SYS}${TARGET_VENDOR}-${TARGET_OS}"
|