ExternalVendorCode/crosstool-ng
1
0
Fork 0
mirror of https://github.com/crosstool-ng/crosstool-ng.git synced 2024-12-22 06:07:49 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
4cbd409508
crosstool-ng/config/debug/gdb.in

21 lines
541 B
Plaintext
Raw Normal View History

Debug facilities: - add a framework to easily add new ones - add gdb as a first debug facility - add patches for gdb After the kernel checked its installed headers, clean up the mess of .checked.* files. Reorder scripts/crosstool.sh: - dump the configuration early - renice early - get info about build system early, when setting up the environment - when in cross or native, the host tools are those of the build system, and only in this case - elapsed time calculations moved to scripts/functions Remove handling of the color: it's gone once and for all. Update tools/addToolVersion.sh: - handle debug facilities - commonalise some code - remove dead tools (cygwin, tcc) Point to my address for bug reports.
2007-05-17 16:22:51 +00:00
# GDB menu
config: fix recursive deps The latest kconfig stuff is more stringent when it comes to validating the dependency of the symbols. It is no longer possible to have a symbol depend on itself (such as our construct for arch/cc/libc/... was doing). Fix our generated-file infrastructure to avoid these situations when the new kconfig stuff will be merged (in a following changeset). Signed-off-by: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
2011-05-08 17:02:44 +00:00
## help gdb is the GNU debugger
Debug facilities: - add a framework to easily add new ones - add gdb as a first debug facility - add patches for gdb After the kernel checked its installed headers, clean up the mess of .checked.* files. Reorder scripts/crosstool.sh: - dump the configuration early - renice early - get info about build system early, when setting up the environment - when in cross or native, the host tools are those of the build system, and only in this case - elapsed time calculations moved to scripts/functions Remove handling of the color: it's gone once and for all. Update tools/addToolVersion.sh: - handle debug facilities - commonalise some code - remove dead tools (cygwin, tcc) Point to my address for bug reports.
2007-05-17 16:22:51 +00:00
debug/gdb: split menuconfig for easier maintenance
2010-03-15 20:42:55 +00:00
source "config/debug/gdb.in.cross"
source "config/debug/gdb.in.native"
Merge r1432:1437 from /branches/newlib into /trunk : - under bare-metal, the user is responsible for providing a gdbserver stub (r1433) - install a CT_TARGET-cc -> CT_TARGET-gcc symlink for the core gcc (r1434) - allow broader dependency in generated config files (r1435, r1436) - prepare C library menuconfig for using a C library under bare-metal (r1437) /trunk/scripts/build/cc/gcc.sh | 4 4 0 0 ++++ /trunk/config/debug/gdb.in | 5 5 0 0 +++++ /trunk/config/libc/glibc.in | 1 1 0 0 + /trunk/config/libc/uClibc.in | 1 1 0 0 + /trunk/config/libc/eglibc.in | 2 1 1 0 +- /trunk/config/config.mk | 20 8 12 0 ++++++++------------ /trunk/config/arch/sh.in | 2 1 1 0 +- /trunk/config/arch/ia64.in | 2 1 1 0 +- /trunk/config/arch/powerpc64.in | 2 1 1 0 +- /trunk/config/libc.in | 4 0 4 0 ---- 10 files changed, 23 insertions(+), 20 deletions(-)
2009-03-26 18:58:13 +00:00
Restore a missing GDB option (whether GDB has --disable-build-with-cxx) and use it. Signed-off-by: Alexey Neyman <stilor@att.net>
2018-05-06 22:20:50 +00:00
sparc-leon: restrict to GDB9 Starting with GDB10, it requires support for std::future<> in the compiler. Such support has not been available on some architectures until GCC9 (see PR 64735). I haven't determined the exact list of affected architectures, so decided to make it a broad dependency: for GDB10+, you need GCC9+. Signed-off-by: Alexey Neyman <stilor@att.net>
2022-02-04 18:31:25 +00:00
# GDB10 and newer require std::future<> which was not implemented on some
# architectures until GCC9; see GCC PR 64735.
config GDB_DEP_NO_STD_FUTURE
def_bool y
depends on !GCC_9_or_later
gdb: use single-number versions/milestones for 9+ Starting with GDB9, the release number is only two numbers (with the last being patchlevel). Therefore, keep two numbers for releases 8 and below, but just a single number for 9 and up. Signed-off-by: Alexey Neyman <stilor@att.net>
2022-02-04 19:35:52 +00:00
select GDB_REQUIRE_older_than_10
sparc-leon: restrict to GDB9 Starting with GDB10, it requires support for std::future<> in the compiler. Such support has not been available on some architectures until GCC9 (see PR 64735). I haven't determined the exact list of affected architectures, so decided to make it a broad dependency: for GDB10+, you need GCC9+. Signed-off-by: Alexey Neyman <stilor@att.net>
2022-02-04 18:31:25 +00:00
gdb: Add gdb-10.2 In GDB 10.x gdbserver was promoted to the top-level folder, see https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=919adfe8409211c726c1d05b47ca59890ee648f1 Which means it is no longer a subfolder in "gdb" and so we have to build gdbserver now exactly in the same way as normal native GDB. One interesting detail is gdbserver doesn't need to deal with target description in .xml so it doesn't depend on libexpat on target, thus we need to move libexpat explicit selection from do_gdb_backend() to its callers when building native [full] gdb as well as cross-gdb for the host. Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> [cp: support old/new layout, regenerate patches] Signed-off-by: Chris Packham <judge.packham@gmail.com>
2020-05-27 10:10:31 +00:00
# As of GDB 10.x gdbserver is now at the toplevel of the distributed
# tarball (instead of a subdirectory of gdb)
config GDB_GDBSERVER_TOPLEVEL
def_bool y
gdb: use single-number versions/milestones for 9+ Starting with GDB9, the release number is only two numbers (with the last being patchlevel). Therefore, keep two numbers for releases 8 and below, but just a single number for 9 and up. Signed-off-by: Alexey Neyman <stilor@att.net>
2022-02-04 19:35:52 +00:00
depends on GDB_10_or_later
Reference in New Issue Copy Permalink