buildroot-novena/toolchain/gdb, branch 2012.02_rc3

gdb: add 7.4, mark 7.1 as deprecated

2012-01-24T21:28:47+00:00

Signed-off-by: Peter Korsgaard

gdb: also force ELF support for gdbhost

2012-01-24T11:46:37+00:00

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:52+00:00

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:00+00:00

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:57+00:00

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:39+00:00

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

gdb: add 7.2a version

2011-10-05T14:58:55+00:00

Signed-off-by: Peter Korsgaard

toolchain/gdb: fixup version strings

2011-10-05T14:56:53+00:00

The gdb tarballs have been re-released after a GPL compliance issue was found: http://sourceware.org/ml/gdb/2011-09/msg00030.html So all versions were re-packaged. In the process, an 'a' was appended to the version strings, and unlike the binutils people, the gdb folks are not inclined in providing legacy symlinks: http://sourceware.org/ml/gdb/2011-09/msg00036.html So, this patch fixes the issue by renaming version strings. It is to be noted that, although the versions got bumped to include an 'a' at the end, the directory contained in the tarball is still named after the version string without the 'a'. For example: - old version : 6.6 - new version : 6.6a - tarball name : gdb-6.6a.tar.bz2 - directory name : gdb-6.6/ In fact, it does not pose any problem for buildroot, as the extract process explicitly mkdirs the directory to extract into, *and* strips the first level of the tree extracted from the tarball. [Peter: fixup patch to apply to head, don't rename config symbols] Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

toolchain/gdb: strip tarball component when extracting

2011-10-05T14:46:50+00:00

For some tarballs of gdb (see next patch), the extracted directory is *not* named after the version string (eg. gdb-6.6a extract into gdb-6.6/) Create the appropriate directory first, then use --strip-{components,path} when extracting gdb (the same way it is done for the generic package infrastructure). At the same time, get rid of the snapshot special case, because: 1- it's no longer available in the menu 2- it would be handled by the above change Signed-off-by: "Yann E. MORIN" Signed-off-by: Peter Korsgaard

gdb: misc cleanup

2011-10-05T14:14:26+00:00

Only use 6.6 on bfin, remove 6.7.1, mark 6.8 + 7.0 as deprecated and default to 7.3. Signed-off-by: Peter Korsgaard