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

82 lines
2.2 KiB
Plaintext
Raw Normal View History

package/gdb: ARC version has stringent dependencies on host gcc 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" <yann.morin.1998@free.fr> Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-02 19:14:05 +01:00
config BR2_PACKAGE_HOST_GDB_ARCH_SUPPORTS
bool
default y
depends on !((BR2_arm || BR2_armeb) && BR2_BINFMT_FLAT)
depends on !BR2_microblaze
toolchain: configs: improve toolchain config readability Add (or move) comment lines in toolchain-related Config.in files to improve readability of the toolchain config section. Source linux-headers/Config.in.host after toolchain-buildroot items. For toolchain-buildroot case, the config file now looks like this: * * Toolchain * * * Toolchain Buildroot Options * * * Kernel Header Options * * * uClibc Options * * * Binutils Options * * * GCC Options * * * Host GDB Options * * * Toolchain Generic Options * Signed-off-by: Petri Gynther <pgynther@google.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-08-08 20:34:59 +02:00
comment "Host GDB Options"
package/gdb: ARC version has stringent dependencies on host gcc 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" <yann.morin.1998@free.fr> Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-02 19:14:05 +01:00
depends on !BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY
depends on BR2_PACKAGE_HOST_GDB_ARCH_SUPPORTS
toolchain: configs: improve toolchain config readability Add (or move) comment lines in toolchain-related Config.in files to improve readability of the toolchain config section. Source linux-headers/Config.in.host after toolchain-buildroot items. For toolchain-buildroot case, the config file now looks like this: * * Toolchain * * * Toolchain Buildroot Options * * * Kernel Header Options * * * uClibc Options * * * Binutils Options * * * GCC Options * * * Host GDB Options * * * Toolchain Generic Options * Signed-off-by: Petri Gynther <pgynther@google.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-08-08 20:34:59 +02:00
gdb: convert to the package infrastructure This commit converts gdb to the package infrastructure, and therefore moves it from toolchain/gdb to package/gdb. The target package is now visible in "Package selection for the target" => "Debugging, profiling and benchmark". The main option, "gdb", forcefully selects the "gdbserver" sub-option by default. Another sub-option, "full debugger" allows to install the complete gdb on the target. When this option is enabled, then "gdbserver" is no longer forcefully selected. This ensures that at least gdbserver or the full debugger gets built/installed, so that the package is not a no-op. The host debugger is still enabled through a configuration option in "Toolchain". It is now visible regardless of the toolchain type (it used to be hidden for External Toolchains). The configuration options relative to the host debugger are now in package/gdb/Config.in.host, similar to how we have package/binutils/Config.in.host. Since gdb is now a proper package, it is no longer allowed to 'select BR2_PTHREADS_DEBUG' to ensure thread debugging is available when needed. Instead, it now 'depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG'. This option, in turn, is selected by the different toolchain backends when appropriate. The 'BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED' option is removed, since we no longer need to know when it is allowed to 'select BR2_PTHREADS_DEBUG'. Also, the 'BR2_PTHREADS_DEBUG' option is moved to appear right below the thread implementation selection (in the case of the Buildroot toolchain backend). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-07 02:04:33 +02:00
config BR2_PACKAGE_HOST_GDB
bool "Build cross gdb for the host"
gdb: do not allow gdbserver/cross-gdb build in some cases When an external toolchain is used, and the user has chosen to copy the external toolchain gdbserver to the target, then we should allow the user to build a gdbserver and/or a cross-gdb: the ones of the external toolchain should be used. The reasoning is that one must use a gdbserver and cross-gdb of identical versions to be sure that debugging will work properly. Change suggested by Yann E. Morin. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-07 02:04:34 +02:00
# When the external toolchain gdbserver is used, we shouldn't
# allow to build a cross-gdb, as the one of the external
# toolchain should be used.
depends on !BR2_TOOLCHAIN_EXTERNAL_GDB_SERVER_COPY
package/gdb: ARC version has stringent dependencies on host gcc 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" <yann.morin.1998@free.fr> Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-02 19:14:05 +01:00
depends on BR2_PACKAGE_HOST_GDB_ARCH_SUPPORTS
gdb: convert to the package infrastructure This commit converts gdb to the package infrastructure, and therefore moves it from toolchain/gdb to package/gdb. The target package is now visible in "Package selection for the target" => "Debugging, profiling and benchmark". The main option, "gdb", forcefully selects the "gdbserver" sub-option by default. Another sub-option, "full debugger" allows to install the complete gdb on the target. When this option is enabled, then "gdbserver" is no longer forcefully selected. This ensures that at least gdbserver or the full debugger gets built/installed, so that the package is not a no-op. The host debugger is still enabled through a configuration option in "Toolchain". It is now visible regardless of the toolchain type (it used to be hidden for External Toolchains). The configuration options relative to the host debugger are now in package/gdb/Config.in.host, similar to how we have package/binutils/Config.in.host. Since gdb is now a proper package, it is no longer allowed to 'select BR2_PTHREADS_DEBUG' to ensure thread debugging is available when needed. Instead, it now 'depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG'. This option, in turn, is selected by the different toolchain backends when appropriate. The 'BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED' option is removed, since we no longer need to know when it is allowed to 'select BR2_PTHREADS_DEBUG'. Also, the 'BR2_PTHREADS_DEBUG' option is moved to appear right below the thread implementation selection (in the case of the Buildroot toolchain backend). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-07 02:04:33 +02:00
help
Build a cross gdb that runs on the host machine and debugs
programs running on the target. It requires 'gdbserver'
installed on the target, see BR2_PACKAGE_GDB_SERVER to
enable it.
if BR2_PACKAGE_HOST_GDB
host-gdb: enable terminal user interface support Add a configuration option to compile host-gdb with the --enable-tui switch. Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-08-29 21:42:31 +02:00
config BR2_PACKAGE_HOST_GDB_TUI
gdb: reword prompt for host TUI option There is no need to name the option "GDB TUI support", since this option is already visible "below" GDB in menuconfig/xconfig. Naming it "TUI support" is therefore sufficient. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-09-15 22:50:08 +02:00
bool "TUI support"
host-gdb: enable terminal user interface support Add a configuration option to compile host-gdb with the --enable-tui switch. Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-08-29 21:42:31 +02:00
help
This option enables terminal user interface (TUI) for gdb
package/gdb: add support for host-gdb with python3 host-gdb was limited to link only with Python 2 although it's possible to build Python 3 for host. Add the ability to link with Python 3. Signed-off-by: Ramon Fried <rfried.dev@gmail.com> [Thomas: add an option to the choice to not have Python support] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-03-23 07:46:21 +01:00
config BR2_PACKAGE_HOST_GDB_PYTHON3
package/gdb: remove python2 support Since at least gdb 7.8, python3 support has been available. As part of the progressive retiring of python2 support, it is time to drop its support in gdb by: - Removing BR2_PACKAGE_HOST_GDB_PYTHON in package/gdb/Config.in.host and removing the choice to leave just a BR2_PACKAGE_HOST_GDB_PYTHON3 option. - Adding BR2_PACKAGE_HOST_GDB_PYTHON to Config.in.legacy - Changing depends on BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3 to depends on BR2_PACKAGE_PYTHON3 in package/gdb/Config.in Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-01-04 21:09:04 +01:00
bool "Python support"
package/gdb: add support for host-gdb with python3 host-gdb was limited to link only with Python 2 although it's possible to build Python 3 for host. Add the ability to link with Python 3. Signed-off-by: Ramon Fried <rfried.dev@gmail.com> [Thomas: add an option to the choice to not have Python support] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-03-23 07:46:21 +01:00
help
This option enables the Python 3 support in the cross gdb.
gdb: enable simulator support for host build Add an option to enable GDB simulator support, so it can be used to test some no-MMU systems. Newer GDB Blackfin Simulator need a workaround for in-tree compile. It doesn't break for older Buildroot supported GDB Blackfin Simulator. Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-31 23:01:36 +02:00
config BR2_PACKAGE_HOST_GDB_SIM
bool "Simulator support"
gdb: drop support for Microblaze 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 <thomas.petazzoni@free-electrons.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Acked-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2017-08-03 23:58:12 +02:00
depends on !BR2_arc
gdb: enable simulator support for host build Add an option to enable GDB simulator support, so it can be used to test some no-MMU systems. Newer GDB Blackfin Simulator need a workaround for in-tree compile. It doesn't break for older Buildroot supported GDB Blackfin Simulator. Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-31 23:01:36 +02:00
help
This option enables the simulator support in the cross gdb.
gdb: convert to the package infrastructure This commit converts gdb to the package infrastructure, and therefore moves it from toolchain/gdb to package/gdb. The target package is now visible in "Package selection for the target" => "Debugging, profiling and benchmark". The main option, "gdb", forcefully selects the "gdbserver" sub-option by default. Another sub-option, "full debugger" allows to install the complete gdb on the target. When this option is enabled, then "gdbserver" is no longer forcefully selected. This ensures that at least gdbserver or the full debugger gets built/installed, so that the package is not a no-op. The host debugger is still enabled through a configuration option in "Toolchain". It is now visible regardless of the toolchain type (it used to be hidden for External Toolchains). The configuration options relative to the host debugger are now in package/gdb/Config.in.host, similar to how we have package/binutils/Config.in.host. Since gdb is now a proper package, it is no longer allowed to 'select BR2_PTHREADS_DEBUG' to ensure thread debugging is available when needed. Instead, it now 'depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG'. This option, in turn, is selected by the different toolchain backends when appropriate. The 'BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED' option is removed, since we no longer need to know when it is allowed to 'select BR2_PTHREADS_DEBUG'. Also, the 'BR2_PTHREADS_DEBUG' option is moved to appear right below the thread implementation selection (in the case of the Buildroot toolchain backend). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-07 02:04:33 +02:00
choice
prompt "GDB debugger Version"
package/gdb: switch to gdb 10.x as the default When doing this, we can simplify the RISC-V related logic. Indeed, as there was no support for RISC-V in gdb 9.x, which was the current default, we had some trickery in the Config.in file to ensure gdb 10.x was used by default on RISC-V. However now that 10.x is the default for everybody, this trickery is no longer needed. Also, we now needs to enable BR2_PACKAGE_GDB_TOPLEVEL when host-gdb is not built, as the default target gdb version is 10.x, and threfore requires BR2_PACKAGE_GDB_TOPLEVEL=y. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-10-09 21:16:43 +02:00
default BR2_GDB_VERSION_10
gdb: Add support for ARC-specific gdb Signed-off-by: Mischa Jonker <mjonker@synopsys.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2013-07-30 11:37:13 +02:00
depends on !BR2_arc
gdb: convert to the package infrastructure This commit converts gdb to the package infrastructure, and therefore moves it from toolchain/gdb to package/gdb. The target package is now visible in "Package selection for the target" => "Debugging, profiling and benchmark". The main option, "gdb", forcefully selects the "gdbserver" sub-option by default. Another sub-option, "full debugger" allows to install the complete gdb on the target. When this option is enabled, then "gdbserver" is no longer forcefully selected. This ensures that at least gdbserver or the full debugger gets built/installed, so that the package is not a no-op. The host debugger is still enabled through a configuration option in "Toolchain". It is now visible regardless of the toolchain type (it used to be hidden for External Toolchains). The configuration options relative to the host debugger are now in package/gdb/Config.in.host, similar to how we have package/binutils/Config.in.host. Since gdb is now a proper package, it is no longer allowed to 'select BR2_PTHREADS_DEBUG' to ensure thread debugging is available when needed. Instead, it now 'depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG'. This option, in turn, is selected by the different toolchain backends when appropriate. The 'BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED' option is removed, since we no longer need to know when it is allowed to 'select BR2_PTHREADS_DEBUG'. Also, the 'BR2_PTHREADS_DEBUG' option is moved to appear right below the thread implementation selection (in the case of the Buildroot toolchain backend). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-07 02:04:33 +02:00
help
Select the version of gdb you wish to use.
package/gdb: bump to version 9.2 The in-tree build restriction has been added after the move of gnulib to top level [1] [2]. This restriction has been added as a workaround a build issue with gdbserver that still uses its own copy of gnulib. gnulib is configured a second time if we build in-tree gdb and gdbserver: configure: error: source directory already configured; run "make distclean" there first configure: error: .././../../gnulib/configure failed for build-gnulib-gdbserver configure: error: ./configure failed for gdbserver Use the same pre-configure-hook as gcc package. Older gdb version support building out of tree even if it's not required. There is no in-tree build restriction of we only build gdbserver for the target. [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=73cc72729a184f00bf6fc4d74684a8516ba6b683 [2] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=043a0010933a6b55081535ecaf7fde9cc1491be0 See: https://sourceware.org/pipermail/gdb-announce/2020/000122.html https://sourceware.org/pipermail/gdb-announce/2020/000123.html Signed-off-by: Maxim Kochetkov <fido_max@inbox.ru> [Romain: - add in-tree build support - improve commit log] Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-05 16:03:37 +02:00
config BR2_GDB_VERSION_9_2
bool "gdb 9.2.x"
package/gdb: enable gdbserver support for riscv It turn out that gdbserver support for riscv is available since 10.1 release, since commit [1]. Restrict the gdb version choice for riscv to 10.1 for simplicity [2]. [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=bf84f7066626c78884436e1c39fb60f04c665f21 [2] http://lists.busybox.net/pipermail/buildroot/2021-June/312681.html Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Alistair Francis <alistair.francis@wdc.com> Reviewed-by: Alistair Francis <alistair.francis@wdc.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-06-17 23:42:13 +02:00
# gdbserver support missing
depends on !BR2_riscv
package/gdb: bump to version 9.2 The in-tree build restriction has been added after the move of gnulib to top level [1] [2]. This restriction has been added as a workaround a build issue with gdbserver that still uses its own copy of gnulib. gnulib is configured a second time if we build in-tree gdb and gdbserver: configure: error: source directory already configured; run "make distclean" there first configure: error: .././../../gnulib/configure failed for build-gnulib-gdbserver configure: error: ./configure failed for gdbserver Use the same pre-configure-hook as gcc package. Older gdb version support building out of tree even if it's not required. There is no in-tree build restriction of we only build gdbserver for the target. [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=73cc72729a184f00bf6fc4d74684a8516ba6b683 [2] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=043a0010933a6b55081535ecaf7fde9cc1491be0 See: https://sourceware.org/pipermail/gdb-announce/2020/000122.html https://sourceware.org/pipermail/gdb-announce/2020/000123.html Signed-off-by: Maxim Kochetkov <fido_max@inbox.ru> [Romain: - add in-tree build support - improve commit log] Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-05 16:03:37 +02:00
package/gdb: add support for gdb 10.x All patches from gdb 9.2 are kept, except 0006-sim-ppc-Fix-linker-error-with-fno-common.patch which is upstream. The other patches are rebased to accommodate some code re-organization in gdb 10.x, especially the move of the gdbserver code from gdb/gdbserver/ to gdbserver/. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-12-28 21:10:22 +01:00
config BR2_GDB_VERSION_10
bool "gdb 10.x"
package/gdb: add support for gdb 11.x All patch from gdb 10.2 are kept. Starting from version 11.x, gdb needs the gmp library. The target variant needs a bit of care: if BR2_GDB_VERSION_11 is not set, either the host gdb is not enabled, in which case the default for the target gdb is 9.x, or the host gdb is enabled, and another version is selected. Signed-off-by: Michael Fischer <mf@go-sys.de> [Thomas: - fix how the gmp dependency is handled - set BR2_PACKAGE_GDB_TOPLEVEL to y for gdb 11.x - fix how BR2_GDB_VERSION is set for gdb 11.x] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> [yann.morin.1998@free.fr: - only select target gmp if using gdb 11 ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-10-09 21:16:42 +02:00
config BR2_GDB_VERSION_11
bool "gdb 11.x"
gdb: convert to the package infrastructure This commit converts gdb to the package infrastructure, and therefore moves it from toolchain/gdb to package/gdb. The target package is now visible in "Package selection for the target" => "Debugging, profiling and benchmark". The main option, "gdb", forcefully selects the "gdbserver" sub-option by default. Another sub-option, "full debugger" allows to install the complete gdb on the target. When this option is enabled, then "gdbserver" is no longer forcefully selected. This ensures that at least gdbserver or the full debugger gets built/installed, so that the package is not a no-op. The host debugger is still enabled through a configuration option in "Toolchain". It is now visible regardless of the toolchain type (it used to be hidden for External Toolchains). The configuration options relative to the host debugger are now in package/gdb/Config.in.host, similar to how we have package/binutils/Config.in.host. Since gdb is now a proper package, it is no longer allowed to 'select BR2_PTHREADS_DEBUG' to ensure thread debugging is available when needed. Instead, it now 'depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG'. This option, in turn, is selected by the different toolchain backends when appropriate. The 'BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED' option is removed, since we no longer need to know when it is allowed to 'select BR2_PTHREADS_DEBUG'. Also, the 'BR2_PTHREADS_DEBUG' option is moved to appear right below the thread implementation selection (in the case of the Buildroot toolchain backend). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-07 02:04:33 +02:00
endchoice
gdb: move version selection from gdb.mk to Config.in.host This avoids duplication of the version selection between these two files. Cc: Spenser Gilliland <spenser@gillilanding.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2014-01-29 22:44:41 +01:00
endif
package/gdb: improve gdb version choice comment The comment has been introduced by commit [1] where the latest gdb version has been used when cross-gdb is not enabled. But since then the gdb package doesn't use the latest gdb version when cross-gdb is not enabled. It's the "stable" version. [1] https://git.buildroot.net/buildroot/commit/?id=fda818390b5e6a585608f4523356eafa0c587f53 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-06-06 17:03:51 +02:00
# If cross-gdb is not enabled, the latest stable version is chosen.
gdb: convert to the package infrastructure This commit converts gdb to the package infrastructure, and therefore moves it from toolchain/gdb to package/gdb. The target package is now visible in "Package selection for the target" => "Debugging, profiling and benchmark". The main option, "gdb", forcefully selects the "gdbserver" sub-option by default. Another sub-option, "full debugger" allows to install the complete gdb on the target. When this option is enabled, then "gdbserver" is no longer forcefully selected. This ensures that at least gdbserver or the full debugger gets built/installed, so that the package is not a no-op. The host debugger is still enabled through a configuration option in "Toolchain". It is now visible regardless of the toolchain type (it used to be hidden for External Toolchains). The configuration options relative to the host debugger are now in package/gdb/Config.in.host, similar to how we have package/binutils/Config.in.host. Since gdb is now a proper package, it is no longer allowed to 'select BR2_PTHREADS_DEBUG' to ensure thread debugging is available when needed. Instead, it now 'depends on BR2_TOOLCHAIN_HAS_THREADS_DEBUG'. This option, in turn, is selected by the different toolchain backends when appropriate. The 'BR2_TOOLCHAIN_HAS_THREADS_DEBUG_IF_NEEDED' option is removed, since we no longer need to know when it is allowed to 'select BR2_PTHREADS_DEBUG'. Also, the 'BR2_PTHREADS_DEBUG' option is moved to appear right below the thread implementation selection (in the case of the Buildroot toolchain backend). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-04-07 02:04:33 +02:00
config BR2_GDB_VERSION
string
toolchain: update ARC tools to arc-2020.09-release This commit bumps ARC toolchain to arc-2020.09-release. ARC GNU tools of version arc-2020.09-release bring some quite significant changes like: * Binutils 2.34.50 with additional ARC patches * GCC 10.0.2 with additional ARC patches * GDB 10.0.50 with additional ARC patches Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: arc-buildroot@synopsys.com Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-11-02 15:50:54 +01:00
default "arc-2020.09-release-gdb" if BR2_arc
package/gdb: switch to gdb 10.x as the default When doing this, we can simplify the RISC-V related logic. Indeed, as there was no support for RISC-V in gdb 9.x, which was the current default, we had some trickery in the Config.in file to ensure gdb 10.x was used by default on RISC-V. However now that 10.x is the default for everybody, this trickery is no longer needed. Also, we now needs to enable BR2_PACKAGE_GDB_TOPLEVEL when host-gdb is not built, as the default target gdb version is 10.x, and threfore requires BR2_PACKAGE_GDB_TOPLEVEL=y. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-10-09 21:16:43 +02:00
default "9.2" if BR2_GDB_VERSION_9_2
default "10.2" if BR2_GDB_VERSION_10 || !BR2_PACKAGE_HOST_GDB
package/gdb: bump 11.x version to 11.2 This is a minor corrective release over GDB 11.1, fixing the following issues: PR sim/28302 (gdb fails to build with glibc 2.34) PR build/28318 (std::thread support configure check does not use CXX_DIALECT) PR gdb/28405 (arm-none-eabi: internal-error: ptid_t remote_target::select_thread_for_ambiguous_stop_reply(const target_waitstatus*): Assertion `first_resumed_thread != nullptr' failed) PR tui/28483 ([gdb/tui] breakpoint creation not displayed) PR build/28555 (uclibc compile failure since commit 4655f8509fd44e6efabefa373650d9982ff37fd6) PR rust/28637 (Rust characters will be encoded using DW_ATE_UTF) PR gdb/28758 (GDB 11 doesn't work correctly on binaries with a SHT_RELR (.relr.dyn) section) PR gdb/28785 (Support SHT_RELR (.relr.dyn) section) Drop patch 0006-sim-filter-out-SIGSTKSZ-PR-sim-28302.patch, which was merged upstream as commit 17d6f2152b583cdc7defafa7813b727a304bac5b. Drop patch 0008-Fix-build-on-rhES5.patch, which was merged upstream as commit df9ebc472a162306dee8ba6e02b99963c2babb7c? Drop patch 0009-gdbserver-aarch64-support.patch, which was merged upstream as commit eb79b2318066cafb75ffdce310e3bbd44f7c79e3. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-02-13 23:01:15 +01:00
default "11.2" if BR2_GDB_VERSION_11
packages/g*/Config.in: fix ordering of statements The check-package script when ran gives warnings on ordering issues on all of these Config files. This patch cleans up all warnings related to the ordering in the Config files for packages starting with the letter g in the package directory. The appropriate ordering is: type, default, depends on, select, help See http://nightly.buildroot.org/#_config_files for more information. Signed-off-by: Adam Duskett <Adamduskett@outlook.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-22 19:17:54 +02:00
depends on BR2_PACKAGE_GDB || BR2_PACKAGE_HOST_GDB
package/gdb: fix build of gdb on riscv Build of gdb on riscv without host-gdb is broken since commit 4ecd247ead22a6cfb87a4ffafc4be05201328aef because BR2_GDB_VERSION_10 is never defined if BR2_PACKAGE_HOST_GDB is not selected resulting in the following build failure: /bin/bash: line 0: cd: /tmp/instance-0/output-1/build/gdb-10.1/gdb/gdbserver: No such file or directory So add a BR2_PACKAGE_GDB_TOPLEVEL hidden option as suggested by Thomas Petazzoni. Fixes: - http://autobuild.buildroot.org/results/ce47d616ee79d5f735779570ebc3b4a9c0f64c6a Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-08-15 18:21:06 +02:00
# recent gdb versions (>= 10) have gdbserver moved at the top-level,
# which requires a different build logic.
config BR2_PACKAGE_GDB_TOPLEVEL
bool
default y if BR2_arc
default y if BR2_GDB_VERSION_10
package/gdb: add support for gdb 11.x All patch from gdb 10.2 are kept. Starting from version 11.x, gdb needs the gmp library. The target variant needs a bit of care: if BR2_GDB_VERSION_11 is not set, either the host gdb is not enabled, in which case the default for the target gdb is 9.x, or the host gdb is enabled, and another version is selected. Signed-off-by: Michael Fischer <mf@go-sys.de> [Thomas: - fix how the gmp dependency is handled - set BR2_PACKAGE_GDB_TOPLEVEL to y for gdb 11.x - fix how BR2_GDB_VERSION is set for gdb 11.x] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> [yann.morin.1998@free.fr: - only select target gmp if using gdb 11 ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-10-09 21:16:42 +02:00
default y if BR2_GDB_VERSION_11
package/gdb: switch to gdb 10.x as the default When doing this, we can simplify the RISC-V related logic. Indeed, as there was no support for RISC-V in gdb 9.x, which was the current default, we had some trickery in the Config.in file to ensure gdb 10.x was used by default on RISC-V. However now that 10.x is the default for everybody, this trickery is no longer needed. Also, we now needs to enable BR2_PACKAGE_GDB_TOPLEVEL when host-gdb is not built, as the default target gdb version is 10.x, and threfore requires BR2_PACKAGE_GDB_TOPLEVEL=y. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-10-09 21:16:43 +02:00
default y if !BR2_PACKAGE_HOST_GDB
package/gdb: fix build of gdb on riscv Build of gdb on riscv without host-gdb is broken since commit 4ecd247ead22a6cfb87a4ffafc4be05201328aef because BR2_GDB_VERSION_10 is never defined if BR2_PACKAGE_HOST_GDB is not selected resulting in the following build failure: /bin/bash: line 0: cd: /tmp/instance-0/output-1/build/gdb-10.1/gdb/gdbserver: No such file or directory So add a BR2_PACKAGE_GDB_TOPLEVEL hidden option as suggested by Thomas Petazzoni. Fixes: - http://autobuild.buildroot.org/results/ce47d616ee79d5f735779570ebc3b4a9c0f64c6a Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-08-15 18:21:06 +02:00
depends on BR2_PACKAGE_GDB || BR2_PACKAGE_HOST_GDB
Reference in New Issue Copy Permalink