NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
b1570168d8
kumquat-buildroot/toolchain/gdb/Config.in

107 lines
3.3 KiB
Plaintext
Raw Normal View History

Add some seperators
2004-10-09 07:33:05 +02:00
comment "Gdb Options"
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
config BR2_PACKAGE_GDB
bool "Build gdb debugger for the Target"
depend on ncurses
2004-10-10 03:16:29 +02:00
select BR2_PACKAGE_NCURSES
toolchain/gdb: target-gdb needs wchar support in toolchain For the embedded readline/gettext stuff. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-04-19 11:05:30 +02:00
depends on BR2_USE_WCHAR
target gdb: depend on thread support 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-13 09:55:56 +01:00
depends on BR2_TOOLCHAIN_HAS_THREADS
gdb: target gdb not available on microblaze Fixes http://autobuild.buildroot.org/results/5950c95ca12721dd910ad72fe52bfa9ac45a5120/build-end.log Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-10-12 08:30:35 +02:00
depends on !BR2_sh && !BR2_sh64 && !BR2_avr32 && !BR2_microblaze
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
help
Patch from acmay: http://bugs.uclibc.org/view.php?id=50 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.
2005-01-23 12:09:40 +01:00
Build the full gdb debugger to run on the target.
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
toolchain/gdb: target-gdb needs wchar support in toolchain For the embedded readline/gettext stuff. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-04-19 11:05:30 +02:00
comment "Gdb debugger for the target needs WCHAR support in toolchain"
toolchain/gdb: fix WCHAR typo Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-10-01 16:41:05 +02:00
depends on !BR2_USE_WCHAR
toolchain/gdb: target-gdb needs wchar support in toolchain For the embedded readline/gettext stuff. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-04-19 11:05:30 +02:00
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
config BR2_PACKAGE_GDB_SERVER
bool "Build gdb server for the Target"
debug: provide an option to copy the gdbserver to the target 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 <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-03-14 23:49:57 +01:00
depends on !BR2_TOOLCHAIN_EXTERNAL
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
help
Patch from acmay: http://bugs.uclibc.org/view.php?id=50 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.
2005-01-23 12:09:40 +01:00
Build the gdbserver stub to run on the target.
A full gdb is needed to debug the progam.
debug: provide an option to copy the gdbserver to the target 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 <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-03-14 23:49:57 +01:00
config BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY
bool "Copy gdb server to the Target"
depends on BR2_TOOLCHAIN_EXTERNAL
help
Copy the gdbserver provided by the external toolchain to the
target.
akvadrako writes: 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.
2006-04-06 20:08:44 +02:00
config BR2_PACKAGE_GDB_HOST
bool "Build gdb for the Host"
gdb: disallow GDB_HOST on external toolchain builds 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-07-29 09:38:20 +02:00
# cross-gdb is supposed to be part of the external
# toolchain. And the build currently fails.
depends on !BR2_TOOLCHAIN_EXTERNAL
Patch from acmay: http://bugs.uclibc.org/view.php?id=50 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.
2005-01-23 12:09:40 +01:00
help
akvadrako writes: 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.
2006-04-06 20:08:44 +02:00
Build gdb to run on the host to debug programs run on the target.
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
choice
i kan spel, can u?
2005-06-25 21:01:23 +02:00
prompt "GDB debugger Version"
gdb: fix version logic for bfin GDB should default to 6.6 on bfin, not on !bfin. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-11-23 23:31:23 +01:00
default BR2_GDB_VERSION_6_6 if BR2_bfin
gdb: add avr32 special verson * 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-12-14 11:38:58 +01:00
default BR2_GDB_VERSION_6_7_1_AVR32_2_1_5 if BR2_avr32
gdb: add 7.4, mark 7.1 as deprecated Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-01-24 22:28:47 +01:00
default BR2_GDB_VERSION_7_4
akvadrako writes: 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.
2006-04-06 20:08:44 +02:00
depends on BR2_PACKAGE_GDB || BR2_PACKAGE_GDB_SERVER || BR2_PACKAGE_GDB_HOST
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
help
Bug #110, acmay writes: The gdb version depends on BR2_HOST_GDB, but it should be BR2_PACKAGE_GDB_CLIENT.
2005-03-21 03:33:24 +01:00
Select the version of gdb you wish to use.
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
- add gdb-6.6
2007-05-15 13:33:08 +02:00
config BR2_GDB_VERSION_6_6
bool "gdb 6.6"
gdb: misc cleanup 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-05 16:14:26 +02:00
depends on BR2_bfin
Add build support for latest gdb
2008-03-30 09:09:07 +02:00
gdb: add avr32 special verson * 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-12-14 11:38:58 +01:00
config BR2_GDB_VERSION_6_7_1_AVR32_2_1_5
depends on BR2_avr32
bool "gdb 6.7.1-avr32-2.1.5"
Add gdb-6.8 support, courtesy Fathi Boudra
2008-07-01 23:36:31 +02:00
config BR2_GDB_VERSION_6_8
bool "gdb 6.8"
gdb: add support for Blackfin gdbserver 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>
2011-02-07 06:49:12 +01:00
depends on !(BR2_avr32 || BR2_bfin)
gdb: misc cleanup 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-05 16:14:26 +02:00
depends on BR2_DEPRECATED
Add gdb-6.8 support, courtesy Fathi Boudra
2008-07-01 23:36:31 +02:00
toolchain/gdb: Add GDB 7.0.1 and 7.1 support Signed-off-by: Paulius Zaleckas <paulius.zaleckas@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-04-29 21:44:20 +02:00
config BR2_GDB_VERSION_7_0_1
bool "gdb 7.0.1"
gdb: add support for Blackfin gdbserver 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>
2011-02-07 06:49:12 +01:00
depends on !BR2_bfin
gdb: misc cleanup 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-05 16:14:26 +02:00
depends on BR2_DEPRECATED
gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOT 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-24 14:26:52 +01:00
depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED
select BR2_PTHREAD_DEBUG if (BR2_TOOLCHAIN_BUILDROOT && !BR2_PTHREADS_NONE)
toolchain/gdb: Add GDB 7.0.1 and 7.1 support Signed-off-by: Paulius Zaleckas <paulius.zaleckas@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-04-29 21:44:20 +02:00
config BR2_GDB_VERSION_7_1
bool "gdb 7.1"
gdb: add support for Blackfin gdbserver 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>
2011-02-07 06:49:12 +01:00
depends on !BR2_bfin
gdb: add 7.4, mark 7.1 as deprecated Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-01-24 22:28:47 +01:00
depends on BR2_DEPRECATED
gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOT 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-24 14:26:52 +01:00
depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED
select BR2_PTHREAD_DEBUG if (BR2_TOOLCHAIN_BUILDROOT && !BR2_PTHREADS_NONE)
toolchain/gdb: Add GDB 7.0.1 and 7.1 support Signed-off-by: Paulius Zaleckas <paulius.zaleckas@gmail.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-04-29 21:44:20 +02:00
gdb: add 7.2a version Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-10-05 16:58:55 +02:00
config BR2_GDB_VERSION_7_2
bool "gdb 7.2.x"
depends on !BR2_bfin
gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOT 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-24 14:26:52 +01:00
depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED
select BR2_PTHREAD_DEBUG if (BR2_TOOLCHAIN_BUILDROOT && !BR2_PTHREADS_NONE)
gdb: add 7.2a version Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-10-05 16:58:55 +02:00
gdb: bump to 7.3.1 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-10-04 11:05:47 +02:00
config BR2_GDB_VERSION_7_3
bool "gdb 7.3.x"
depends on !BR2_bfin
gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOT 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-24 14:26:52 +01:00
depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED
select BR2_PTHREAD_DEBUG if (BR2_TOOLCHAIN_BUILDROOT && !BR2_PTHREADS_NONE)
gdb: bump to 7.3.1 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-10-04 11:05:47 +02:00
gdb: add 7.4, mark 7.1 as deprecated Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-01-24 22:28:47 +01:00
config BR2_GDB_VERSION_7_4
bool "gdb 7.4.x"
depends on !BR2_bfin
depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED
select BR2_PTHREAD_DEBUG if (BR2_TOOLCHAIN_BUILDROOT && !BR2_PTHREADS_NONE)
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
endchoice
gdb: fix kconfig dependency handling with !BR_TOOLCHAIN_BUILDROOT 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-24 14:26:52 +01:00
comment "gdb 7.x support needs pthread debug support in toolchain"
depends on BR2_PACKAGE_GDB || BR2_PACKAGE_GDB_SERVER || BR2_PACKAGE_GDB_HOST
depends on !BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED
Major buildroot facelift, step one. -Erik
2004-10-09 03:06:03 +02:00
config BR2_GDB_VERSION
string
toolchain/gdb: fixup version strings 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-09-13 23:57:30 +02:00
default "6.6a" if BR2_GDB_VERSION_6_6
gdb: add avr32 special verson * 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-12-14 11:38:58 +01:00
default "6.7.1-avr32-2.1.5" if BR2_GDB_VERSION_6_7_1_AVR32_2_1_5
toolchain/gdb: fixup version strings 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-09-13 23:57:30 +02:00
default "6.8a" if BR2_GDB_VERSION_6_8
default "7.0.1a" if BR2_GDB_VERSION_7_0_1
default "7.1a" if BR2_GDB_VERSION_7_1
gdb: add 7.2a version Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2011-10-05 16:58:55 +02:00
default "7.2a" if BR2_GDB_VERSION_7_2
gdb: bump to 7.3.1 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-10-04 11:05:47 +02:00
default "7.3.1" if BR2_GDB_VERSION_7_3
gdb: bump 7.4.x series to 7.4.1 Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-04-26 16:25:03 +02:00
default "7.4.1" if BR2_GDB_VERSION_7_4
Reference in New Issue Copy Permalink