summaryrefslogtreecommitdiff
path: root/toolchain/gdb/Config.in
AgeCommit message (Collapse)Author
2012-01-24gdb: add 7.4, mark 7.1 as deprecatedPeter Korsgaard
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-11-24gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOTPeter Korsgaard
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 <jacmet@sunsite.dk>
2011-11-23gdb: fix version logic for bfinPeter Korsgaard
GDB should default to 6.6 on bfin, not on !bfin. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-11-13target gdb: depend on thread supportThomas Petazzoni
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 <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-11-13gdb: do not allow native gdb on SuperH architectureThomas Petazzoni
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 <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-10-05gdb: add 7.2a versionPeter Korsgaard
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-10-05toolchain/gdb: fixup version stringsYann E. MORIN
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" <yann.morin.1998@anciens.enib.fr> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-10-05gdb: misc cleanupPeter Korsgaard
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 <jacmet@sunsite.dk>
2011-10-05gdb: bump to 7.3.1Yegor Yefremov
this version fixes compilation issue on some old build systems like openSUSE 10.3 saying some host libraries were too old [Peter: drop bugfix number from config name, similar to kernel-headers] Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-02-07gdb: add support for Blackfin gdbserverMike Frysinger
This requires removing "deprecated" markings from gdb-6.6, but this isn't that big of a deal. That is the last version with Blackfin support at the moment and we're in the process of getting mainlined. [Peter: only mark as undeprecated on bfin] Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Mike Frysinger <vapier@gentoo.org> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-10-01toolchain/gdb: fix WCHAR typoPeter Korsgaard
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-07-29gdb: disallow GDB_HOST on external toolchain buildsThomas Petazzoni
The cross-gdb is supposed to be part of the external toolchain, so Buildroot does not need to build it. Moreover, GDB_HOST build currently fail with: ln -snf ../../bin/arm-unknown-linux-gnueabi-gdb \ /home/test/outputs/test-48/staging/usr/arm-unknown-linux-gnueabi/bin/gdb ln: creating symbolic link `/home/test/outputs/test-48/staging/usr/arm-unknown-linux-gnueabi/bin/gdb': No such file or directory And even worse: they overwrite the cross-gdb of the external toolchain! Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2010-05-03toolchain/gdb: get rid of 6.4 / 6.5Peter Korsgaard
These are ancient (2006) and upstream strongly discourage using them: ftp://sourceware.org/pub/gdb/old-releases/README Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-05-01toolchain/gdb: Add GDB 7.0.1 and 7.1 supportPaulius Zaleckas
Signed-off-by: Paulius Zaleckas <paulius.zaleckas@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-04-19toolchain/gdb: target-gdb needs wchar support in toolchainPeter Korsgaard
For the embedded readline/gettext stuff. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-03-30get rid of broken nios2 supportPeter Korsgaard
Has been marked as broken for more than 1 year, with no indication that anyone cares, and it needs a bunch of special handling. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2009-12-14gdb: do not allow selection of non-avr32 versions on AVR32Thomas Petazzoni
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2009-12-14gdb: add avr32 special versonThomas Petazzoni
* Add a new gdb version for AVR32 in Config.in * Use a special mirror for this gdb version in gdb.mk * Do not try to apply patches when the patch directory does not exist in gdb.mk Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2009-04-28toolchain/gdb: remove ancient deprecated versionsPeter Korsgaard
They shouldn't be used anymore, needs havily patching (6.3 has more than 200k patches) and no one tests them with current toolchains.
2009-04-28toolchain/gdb: remove broken snapshot supportPeter Korsgaard
2008-12-08toolchain/gdb: 6.4 shouldn't be selectable for avr32Peter Korsgaard
2008-12-08toolchain/gdb: mark old versions as deprecatedPeter Korsgaard
2008-12-08toolchain/gdb: default to 6.8Peter Korsgaard
2008-07-17Kconfig: remove 'default n'Peter Korsgaard
'default n' is the default, so there's no need to say it explicitly.
2008-07-04Add prepatched AVR32 gcc-4.2.2 toolchain from www.atmel.no, move patch ↵Ulf Samuelsson
locations for prepatched toolchain to be under the toolchain directory
2008-07-01Add gdb-6.8 support, courtesy Fathi BoudraUlf Samuelsson
2008-03-30Add build support for latest gdbUlf Samuelsson
2008-02-07updated gdb support for nios2, thanks AtleIvan Kuten
2007-09-26- revert some bad checkins, fixup bad settings in atmel targets and move the ↵Bernhard Reutner-Fischer
gcc target abi back to a place where the other arch-specific settings live
2007-07-29gdb config for AVR32Ulf Samuelsson
2007-06-06- adjust to use the gcc-4.2.0 releaseBernhard Reutner-Fischer
- adjust default gdb version to 6.6 - fix stripping gmp/mpfr due to recent LIBTGTEXT changes
2007-05-15- add gdb-6.6Bernhard Reutner-Fischer
2006-06-21version bump to 6.5Mike Frysinger
2006-04-06akvadrako writes:Eric Andersen
The term gdb-client is deceptive - although it parallels the gdb-server name, it is actually a full fledged gdb version. I want to use it to debug uClibc core files on my host system. Although I haven't got that to work yet, I wasted time figuring out how to do build gdb for the host not realizing it already had a target. With this documentation change, things would have been a lot clearer to me.
2005-12-02import gdb-6.4Mike Frysinger
2005-08-30Add in support for downloading and building the latest snapshot of GDB. If ↵"Steven J. Hill"
you want to debug NPTL binaries, you'll need the latest and greatest. Patches for 6.3 will be forward ported where applicable later this week.
2005-06-25i kan spel, can u?"Steven J. Hill"
2005-03-26update gdb a bit. remove support for ancient versions.Eric Andersen
2005-03-21Bug #110, acmay writes: The gdb version depends on BR2_HOST_GDB, but it ↵Mike Frysinger
should be BR2_PACKAGE_GDB_CLIENT.
2005-03-02kill off support for gdb 5.3Eric Andersen
2005-02-27Added support for gdb 6.3. Rediffed 100-uclibc-conf.patch to fixJoakim Tjernlund
obvious rejects.
2005-01-23Patch from acmay: http://bugs.uclibc.org/view.php?id=50Eric Andersen
0000050: gdb_server and gdb_client fixes and split Here is a patch with 2 issues. gdbserver does not depend on ncurses (just the full gdb needs it) Split out gdb client config option, to be separate from gdbserver. If you build gdb client for the host once it does not need to be rebuilt when the rest of libs change. So I build it and save it off.
2004-10-10depend on ncursesEric Andersen
2004-10-09Add some seperatorsEric Andersen
2004-10-09Major buildroot facelift, step one.Eric Andersen
-Erik
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-23 21:50:39 +0000