linux/poky.git/meta/recipes-devtools/gdb, branch rocko-next

gdb: fix header ordering for TRAP_HWBKPT

2018-03-14T14:54:06+00:00

This error can appear in gdb/nat/linux-ptrace.c because of the order in which some headers are processed: | In file included from ../../gdb-7.11.1/gdb/nat/linux-ptrace.c:20:0: | ../../gdb-7.11.1/gdb/nat/linux-ptrace.h:175:22: error: expected identifier before numeric constant | # define TRAP_HWBKPT 4 | ^ | Makefile:2357: recipe for target 'linux-ptrace.o' failed | make[2]: *** [linux-ptrace.o] Error 1 | make[2]: *** Waiting for unfinished jobs.... | make[2]: Leaving directory '/oe/build/tmp-rpb-glibc/work/aarch64-linaro-linux/gdb/7.11.1-r0/build-aarch64-linaro-linux/gdb' | Makefile:8822: recipe for target 'all-gdb' failed | make[1]: *** [all-gdb] Error 2 | make[1]: Leaving directory '/oe/build/tmp-rpb-glibc/work/aarch64-linaro-linux/gdb/7.11.1-r0/build-aarch64-linaro-linux' | Makefile:846: recipe for target 'all' failed | make: *** [all] Error 2 A patch from GDB's current master solves the issue. (From OE-Core rev: 4aaf747099714ec11158571527396ed9e818729e) (From OE-Core rev: 5a4f22a0cb9b1a6151256d009d06e130ddc62573) Signed-off-by: Daniel Díaz Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gdb: fix gdbserver not working in musl/mips context

2017-06-28T14:52:18+00:00

Similar to https://bugs.lede-project.org/index.php?do=details&task_id=637&openedfrom=-1%2Bweek (From OE-Core rev: 0b9d94a5e54191f93659f7b4e7a3cb4376487823) Signed-off-by: André Draszik Acked-by: Sylvain Lemieux Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta: Drop remnants of uclibc support

2017-06-22T08:16:00+00:00

uclibc support was removed a while ago and musl works much better. Start to remove the various overrides and patches related to uclibc which are no longer needed. uclibc support in a layer would still be possible. I have strong reasons to believe nobody is still using uclibc since patches are missing and I doubt the metadata even parses anymore. (From OE-Core rev: 653704e9cf325cb494eb23facca19e9f05132ffd) Signed-off-by: Richard Purdie

gdb: Upgrade to 8.0 release

2017-06-12T14:08:30+00:00

For details on changes see http://lists.gnu.org/archive/html/info-gnu/2017-06/msg00002.html in tcmode-default.inc Pin gdb to 8.0 (From OE-Core rev: caf2f858bf41154c72aba37d58b5a5336e02fbb8) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

recipes/*-cross recipes: ignore TARGET_ARCH sstate hash

2017-04-12T14:09:58+00:00

"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 Signed-off-by: Richard Purdie

gdb-cross: avoid tune specific paths

2017-04-12T14:09:58+00:00

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 Signed-off-by: Richard Purdie

gdb: don't bundle bfd.info -- leave that to binutils.

2017-03-17T16:53:04+00:00

We see: file /usr/share/info/bfd.info conflicts between attempted installs of gdb-doc-7.12.1-r0.core2_64 and binutils-doc-2.28-r0.core2_64 You can't really have gdb and not binutils, so there is no need to do alternatives here ; just clobber the one from gdb and let the binutils one be the default. (From OE-Core rev: 19a825a578e2e705e5502982b787cff54d021359) Signed-off-by: Paul Gortmaker Signed-off-by: Richard Purdie

recipes: Make use of the new bb.utils.filter() function

2017-03-01T11:17:45+00:00

(From OE-Core rev: 0a1427bf9aeeda6bee2cc0af8da4ea5fd90aef6f) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

gdb: Upgrade to 7.12.1

2017-02-23T20:49:49+00:00

Drop already applied patches (From OE-Core rev: 233641857bdc4071e5cb9a25206def880eb2754d) (From OE-Core rev: 3393364d1b365226d15042f20f0e6c56a439225b) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

gdb 7.12: fix armv8b build

2017-02-05T09:22:17+00:00

Backport fix from GDB upstream to fix big-endian aarch64 build. (From OE-Core rev: 0635a96d82f5f5dd65a2d45ddca7559dea847916) Signed-off-by: Koen Kooi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie