Hi all, I tried the new external-arm feature. I had a problem in building gdb-7.8, attached the patch I used to solve the problem,an in the following the patch for the layer, but anyway why gdb-7.8 is still used in the master branch? why do not upgrade to a newer version?
Regards, d.
diff --git a/meta-linaro-toolchain/recipes-devtools/gdb/gdb_linaro-7.8.bb b/meta-linaro-toolchain/recipes-devtools/gdb/gdb_linaro-7.8.bb index 630d43c..841b1ed 100644 --- a/meta-linaro-toolchain/recipes-devtools/gdb/gdb_linaro-7.8.bb +++ b/meta-linaro-toolchain/recipes-devtools/gdb/gdb_linaro-7.8.bb @@ -6,6 +6,8 @@ inherit python-dir PACKAGECONFIG ??= "" PACKAGECONFIG[python] = "--with-python=${WORKDIR}/python,--without-python,python"
+SRC_URI += "file://0001-Fix-compilation-external-gcc-arm-8.2-2018.11.patch" + do_configure_prepend() { if [ -n "${@bb.utils.contains('PACKAGECONFIG', 'python', 'python', '', d)}" ]; then cat > ${WORKDIR}/python << EOF
Diego,
8.2 version of gdb from oe-core builds just fine. linaro-7.8 version of gdb is around for historical reasons, I guess. Similar to linaro-2.20 version of glibc and linaro-2.25 version of binutils...
Thank you Denys, so here is a stupid question: should I change layers priorities or add a PREFERRED_VERSION_gdb = "8.2"? as by default it builds linaro-gdb. By the way I had an issue also with strace 4.24, in oe-core, anyway moving to 4,25 it solved. Thanks in advance, d.
-
Denys Dmytriyenko -
Diego Buffa