mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2025-01-07 05:18:41 +00:00
2f286ce5ab
... it is possible to just not set it in the configuration, why force it? It just increases the complexity in Kconfig. Signed-off-by: Alexey Neyman <stilor@att.net>
38 lines
1.2 KiB
Plaintext
38 lines
1.2 KiB
Plaintext
# Menu for the native GDB
|
|
|
|
config GDB_NATIVE
|
|
bool
|
|
prompt "Native gdb"
|
|
depends on ! BARE_METAL
|
|
select EXPAT_TARGET
|
|
select NCURSES_TARGET
|
|
help
|
|
Build and install a native gdb for the target, to run on the target.
|
|
|
|
if GDB_NATIVE
|
|
|
|
config GDB_NATIVE_STATIC
|
|
bool
|
|
prompt "Build a static native gdb"
|
|
depends on EXPERIMENTAL
|
|
help
|
|
In case you have trouble with dynamic loading of shared libraries,
|
|
you will find that a static gdb comes in handy.
|
|
|
|
However, it has been noticed at least on x86 that enabling this
|
|
option produces an invalid gdb binary. It is linked with
|
|
"-static -Wl,--dynamic-list=..." which
|
|
# (a) requests invalid program interpreter
|
|
# (b) crashes glibc/uClibc-ng and does not work with musl
|
|
# See https://sourceware.org/ml/libc-alpha/2017-03/msg00267.html
|
|
|
|
It is possible it would work with other architectures, hence it is
|
|
not completely removed. Use with care and report to the mailing list
|
|
if the resulting gdbserver works.
|
|
|
|
For further details, see:
|
|
https://sourceware.org/bugzilla/show_bug.cgi?id=19617
|
|
https://sourceware.org/bugzilla/show_bug.cgi?id=21086
|
|
|
|
endif # GDB_NATIVE
|