buildroot-novena/toolchain/gdb, branch 2012.05_rc1

gdb: fix target gdb build when host-gawk is built before

2012-05-07T19:40:31Z

When the crosstool-ng backend is used, host-gawk is built as a dependency of the crosstool-ng package, and therefore an host 'gawk' binary is installed in $(HOST_DIR). When the target gdb package is also selected, this unfortunately leads to a build failure, as reported on http://buildroot.humanoidz.org/results/f19c0499d08212d8b5100fa9434e1197092957db/build-end.log. The problem is that the ./configure of gdb detects gawk in the PATH, but at compile time, it fails to find gawk. This is due to the fact that the gdb compilation process is started without the correct path. This patch fixes this by passing $(TARGET_MAKE_ENV) in the environment of the gdb compilation process. A better fix would be to switch gdb to the AUTOTARGETS infrastructure in the future. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

gdb: bump 7.4.x series to 7.4.1

2012-04-29T08:57:30Z

Signed-off-by: Gustavo Zacarias Signed-off-by: Peter Korsgaard

DOWNLOAD: change $1=DIRECTORY_URL, $2=FILE_NAME to $1=FULL_FILE_URL, $2=FILE_NAME

2012-03-18T21:21:16Z

This modifies the definition of DOWNLOAD to receive two arguments: the first one is the full URL of the file to download, whereas the second (and optional) is the name the file will have once downloaded. Same thing with the SOURCE_CHECK_WGET and SCP functions. All calls to these functions have been changed to the shortest form of the new API, except for toolchains acquisition. Since there is quite a number of different toolchains this call to DOWNLOAD is better set to the generic one. Signed-off-by: Alvaro G. M Acked-by: Arnout Vandecappelle (Essensium/Mind) Tested-by: Stephan Hoffmann Downloading Microblaze LE toolchain works on a clean install Signed-off-by: Peter Korsgaard

debug: provide an option to copy the gdbserver to the target

2012-03-15T22:04:39Z

When an external toolchain is used, it is very likely that it contains a pre-built version of a gdbserver that has the same version as the cross-gdb included in the external toolchain. So, we now provide an option that allows to copy this pre-built gdbserver to the target. As the location of the gdbserver in the external toolchain is not standardized, we only support the CodeSourcery and Crosstool-NG layouts for the moment. Other locations can be added later. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

gdb: add 7.4, mark 7.1 as deprecated

2012-01-24T21:28:47Z

Signed-off-by: Peter Korsgaard

gdb: also force ELF support for gdbhost

2012-01-24T11:46:37Z

Similar to how we do for target (ee39d53ce3ee (Fix GDB BFD test linking)). Gdb comes with an embedded copy of libiberty, but binutils also installs libiberty.a into HOST_DIR. The gdb configure script tries to link against this one rather than the gdb version when it checks for ELF support. This may fail if those versions are not compatible, leading to obscure error messages from gdb at runtime such as: I'm sorry, Dave, I can't do that. Symbol format `elf32-$ARCH' unknown. Fix it by forcing ELF support. Signed-off-by: Peter Korsgaard

gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOT

2011-11-24T13:26:52Z

Newer versions of GDB need pthread debugging support if threads are enabled, which is always the case for glibc but is a configure option for uClibc. We have solved this for internal toolchains by selecting the BR2_PTHREAD_DEBUG option from the GDB selection if needed, but as this option isn't available when ctng/external toolchains are used, mconf prints ugly warnings and the build may fail if an external uClibc toolchain without pthread debugging support is used. Fix it by introducing 2 more hidden config options: - BR2_TOOLCHAIN_HAS_THREADS_DEBUG - BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED The first tells us if the toolchain HAS pthreads debugging support, and is checked by check_uclibc_feature in helper.mk for external uClibc based toolchains. The second tells us if the toolchain is ABLE TO provide pthreads debugging support if threads are enabled, either because it's an internal toolchain where we can force enable it or an external glibc/eglibc toolchain or uClibc with the option enabled. Crosstool-ng forcibly enables this support, so those will always work. The preconfigured uClibc-based toolchains we have also all enable it. Finally, show a comment if this isn't the case so the (external toolchain) user knows why. This is placed outside the choice option, as menuconfig has a bug where it doesn't show choice selections which only contain comments. Signed-off-by: Peter Korsgaard

gdb: fix version logic for bfin

2011-11-23T22:32:00Z

GDB should default to 6.6 on bfin, not on !bfin. Signed-off-by: Peter Korsgaard

target gdb: depend on thread support

2011-11-13T20:32:57Z

Compiling gdb for the target requires thread support in the C library, otherwise: /home/test/outputs/test-888/toolchain/gdb-7.3.1/gdb/gdb_thread_db.h:37:21: fatal error: pthread.h: No such file or directory Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard

gdb: do not allow native gdb on SuperH architecture

2011-11-13T20:31:39Z

The gdb debugger does not have support for running as the native debugger on the SuperH architecture: configure: error: "*** Gdb does not support native target sh4-unknown-linux-gnu" See also http://lists.debian.org/debian-superh/2010/04/msg00000.html. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard