buildroot/package/gdb, branch 2017.11.2

gdb: prevent installation of libbfd.so and libopcode.so

2017-12-27T16:34:56+00:00

The gdb install target installs dynamic versions of libbfd and libopcode, accidentally overwriting the binutils provided versions (gdb itself links against the bundled static ones to avoid version problems, so the dynamic ones are un-needed). Prevent the installation by using the '--disable-install-libbfd' configure option. Signed-off-by: Peter Seiderer Signed-off-by: Thomas Petazzoni (cherry picked from commit b54c7931952874a814e48df75093e13ad955604f) Signed-off-by: Peter Korsgaard

toolchain: Bump ARC tools to arc-2017.09 release

2017-11-03T21:46:06+00:00

This commit finally bumps ARC tools to the most recent arc-2017.09 release version. ARC GNU tools of version arc-2017.09 bring some quite significant changes like: * Binutils v2.29 with additional ARC patches * GCC 7.1.1 with additional ARC patches * glibc 2.26 with additional ARC patches More information on this release could be found here: https://github.com/foss-for-synopsys-dwc-arc-processors/toolchain/releases/tag/arc-2017.09-release Signed-off-by: Evgeniy Didin Cc: Alexey Brodkin Cc: arc-buildroot@synopsys.com Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

package/gdb: ARC version has stringent dependencies on host gcc

2017-11-02T21:37:50+00:00

The ARC gdb version requires a gcc >= 4.8 (because C++11). Since the host variant uses the same sources as the target variant, we must ensure that we have a host gcc >= 4.8 as well. Move the architecture dependencies to their own symbol, and also hide the comment when they are not met. Fixes: http://autobuild.buildroot.net/results/43eae264991aa369490236c7bd59c0b6a67fcf25/ Signed-off-by: "Yann E. MORIN" Cc: Alexey Brodkin Cc: Thomas Petazzoni Signed-off-by: Thomas Petazzoni

toolchain: Bump ARC tools to arc-2017.09-rc1

2017-10-08T14:10:27+00:00

This commit bumps ARC toolchain to arc-2017.09-rc1. The arc-2017.09 series is built on top of upstream GCC 7.1.1 and Binutils 2.29 so please expect all kinds of breakages related to GCC 7.x as we saw earlier with the move from 4.8 to 6.x :) Note patches for both GCC and Binutils were updated with copies from corresponding mainline versions, i.e. "package/gcc/7.2.0" and "package/binutils/2.29". Please note that it is a release candidate and it might contain some breakages, please don't use it for production builds. Signed-off-by: Evgeniy Didin Cc: Alexey Brodkin Cc: arc-buildroot@synopsys.com Cc: Thomas Petazzoni [Thomas: drop binutils patch related to the Blackfin architecture.] Signed-off-by: Thomas Petazzoni

package/gdb: bump to version 8.0.1

2017-10-01T21:15:12+00:00

https://sourceware.org/ml/gdb-announce/2017/msg00004.html Signed-off-by: Romain Naour Signed-off-by: Peter Korsgaard

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