buildroot/package/gdb, branch 2017.08.1

gdb: add fix for gdb 7.12 and gdb 8.0 build on noMMU platforms

2017-08-10T08:26:51+00:00

This adds a patch to gdb 7.12 and gdb 8.x, which fixes the build on noMMU platforms. It is not needed for older versions of gdb, since it's related to the switch of gdb to C++ in the 7.12 release. Fixes: ../nat/linux-ptrace.c: In function 'int linux_fork_to_function(gdb_byte*, int (*)(void*))': ../nat/linux-ptrace.c:273:29: error: invalid conversion from 'void*' to 'gdb_byte* {aka unsigned char*}' [-fpermissive] child_stack = xmalloc (STACK_SIZE * 4); The patch has already been merged upstream, as of commit ffce45d2243e5f52f411e314fc4e1a69f431a81f, and will therefore be part of future gdb releases. Signed-off-by: Thomas Petazzoni Signed-off-by: Arnout Vandecappelle (Essensium/Mind)

gdb: drop support for Microblaze

2017-08-04T20:01:38+00:00

Microblaze support was never upstreamed in gdb. We currently use a gdb from the Xilinx Github repository, but this gdb is based on 7.6, and has never been updated in the last 4 years. There are no other active branches at https://github.com/Xilinx/gdb/branches. Xilinx has a slightly newer gdb, based on 7.7, available at https://github.com/Xilinx/meta-xilinx/tree/master/recipes-microblaze/gdb. However, it's apparently only available in the form of stack of big patches (https://github.com/Xilinx/meta-xilinx/tree/master/recipes-microblaze/gdb/files). Currently, gdb on Microblaze fails to build in various conditions: * Against glibc, with "error: conflicting types for 'ps_lgetfpregs'" * Against musl, with "error: unknown type name 'elf_gregset_t'" While those issues can probably be fixed, the fact that there is no active upstream significantly reduces the incentive to fix those problems. Therefore, let's drop support for gdb on Microblaze entirely. Signed-off-by: Thomas Petazzoni Acked-by: Arnout Vandecappelle (Essensium/Mind) Acked-by: Romain Naour Signed-off-by: Arnout Vandecappelle (Essensium/Mind)

gdb: force to use ncurses and not termcap for host-gdb

2017-08-01T21:37:06+00:00

Both our target and host gdb depend on ncurses (host-ncurses for host-gdb, of course). However, while for the target we passs --with-curses, we are not doing this for the host variant. Due to this, host-gdb default to using the termcap library: if such a library is available on the build system, it will be used instead of the host-ncurses we have built. This causes the host gdb binary to depend on a library that we do not provide in $(HOST_DIR), breaking the principle of a standalone SDK (which should only depend on the C library). To solve this, we simply pass --with-curses in HOST_GDB_CONF_OPTS, which forces host-gdb to use the host-ncurses library. Signed-off-by: Thomas Petazzoni Reviewed-by: Romain Naour Signed-off-by: Thomas Petazzoni

arch/xtensa: accept the overlay to be an URL

2017-07-09T14:58:03+00:00

It can be interesting to get the overlay from a remote server, rather than expect it to be present locally. Since that file can be any URL, we can't know its hash, so we just exclude it. Signed-off-by: "Yann E. MORIN" Signed-off-by: Max Filippov [Thomas: use DL_DIR instead of BR2_DL_DIR.] Signed-off-by: Thomas Petazzoni

arch/xtensa: allow specifying path to tarball file

2017-07-09T13:41:51+00:00

currently, specifying a custom Xtrensa core is done with two variables: - the core name - the directory containing the overlay tarball However, the core name only serves to construct the tarball name, and is not used whatsoever to configure any of the toolchain components (binutils, gcc or gdb), except through the files that are overlayed in their respective source trees. This has two main drawbacks: - the overlay file must be named after the core, - the tarball can not be compressed. Furthermore, it also makes it extremely complex to implement a download of that tarball. So, those two variables can be squeezed into a single variable, that is the complete path of the overlay tarball. Update the qemu-xtensa defconfig accordingly. Note: we do not add a legacy entry for BR2_XTENSA_CORE_NAME, since it was previously a blind option in the last release, and there's been no release since we removed BR2_XTENSA_CUSTOM_NAME. So, we just update the legacy comments for BR2_XTENSA_CUSTOM_NAME, since that's all the user could have seen in any of our releases so far. Signed-off-by: "Yann E. MORIN" Cc: Gustavo Zacarias Signed-off-by: Max Filippov Signed-off-by: Thomas Petazzoni

Globally replace $(HOST_DIR)/usr/bin with $(HOST_DIR)/bin

2017-07-05T13:19:29+00:00

Since things are no longer installed in $(HOST_DIR)/usr, the callers should also not refer to it. This is a mechanical change with git grep -l '$(HOST_DIR)/usr/bin' | xargs sed -i 's%$(HOST_DIR)/usr/bin%$(HOST_DIR)/bin%g' Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

gdb: Remove /usr part from installation path of gdbserver

2017-07-05T09:46:41+00:00

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) Reviewed-by: Romain Naour Signed-off-by: Thomas Petazzoni

gdb: fix full gdb build for MIPS musl

2017-06-19T19:47:05+00:00

Currently building full gdb for MIPS musl fails because it's trying to include which is provided by glibc and uClibc, but not by musl. However, the kernel headers provide which has the same definitions, so we can use that one instead. Backporting a patch that has been sent upstream. Taken from here: https://sourceware.org/bugzilla/show_bug.cgi?id=21070 Signed-off-by: Vicente Olivert Riera Signed-off-by: Thomas Petazzoni

package/gdb: add support for gdb 8.0

2017-06-11T16:02:41+00:00

Add a dependency on gcc >= 4.8 since gdb needs a C++11 compiler. Remove included patch since 7.12.1: 0001-Remove-const-in-xtensa-linux-nat.c-fetch_gregs.patch https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=d274ecf4ddf76768af57e27f654b9ce6784b391c Rebase remaining patches: 0002-ppc-ptrace-Define-pt_regs-uapi_pt_regs-on-GLIBC-syst.patch 0003-sh-ptrace-Define-pt_-dsp-regs-uapi_pt_-dsp-regs-on-G.patch See https://sourceware.org/ml/gdb-announce/2017/msg00003.html Signed-off-by: Romain Naour Signed-off-by: Thomas Petazzoni

gdb: fix build of gdbserver on m68k/coldfire

2017-06-11T16:00:48+00:00

This commit adds a small patch to gdb that fixes the build of gdbserver on m68k/coldfire: ../nat/linux-ptrace.c: In function 'linux_fork_to_function': ../nat/linux-ptrace.c:282:19: warning: implicit declaration of function 'clone' [-Wimplicit-function-declaration] child_pid = clone (function, child_stack + STACK_SIZE, ^ ../nat/linux-ptrace.c:283:5: error: 'CLONE_VM' undeclared (first use in this function) CLONE_VM | SIGCHLD, child_stack + STACK_SIZE * 2); ^ ../nat/linux-ptrace.c:283:5: note: each undeclared identifier is reported only once for each function it appears in Thanks to Waldemar for pointing out the patch fixing this issue. Signed-off-by: Thomas Petazzoni --- Changes since v2: - None Changes since v1: - New patch in the series