mirror of
https://github.com/crosstool-ng/crosstool-ng.git
synced 2024-12-21 21:57:48 +00:00
58c347c781
Back in the day gdbserver was treated as a subproject of GDB and even was located in "gdb/gdbserver" and so to build gdbserver we had to go into "gdb/gdbserver" and there run configure. That way full GDB was out of the picture. Now starting from GDB 10.1 where gdbserver was promoted to the top-level we're supposed to run top-level's configure script for all the tools provided by the unified binutils-gdb tree. That said if we only want to build gdbserver (and that's what we want since we build one tool at a build step) we have to be explicit: ----------------->8---------------- --enable-gdbserver --disable--gdb ----------------->8---------------- Ah, and so far we used to build full native GDB when only wanted gdbserver if it was GDB v10.x ;) Ironically full native/target GDB also enabled gdbserver by default so we need to also disable it explicitly with "--disable-gdbserver". Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> |
||
|---|---|---|
| .. | ||
| build | ||
| override | ||
| upgrade | ||
| compile | ||
| config.guess | ||
| config.rpath | ||
| config.sub | ||
| crosstool-NG.sh | ||
| depcomp | ||
| functions | ||
| install-sh | ||
| ltmain.sh | ||
| missing | ||
| populate.in | ||
| saveSample.sh | ||
| scripts.mk | ||
| show-config.sh | ||
| show-tuple.sh | ||
| toolchain-config.in | ||
| version-check.sh | ||
| xldd.in | ||