diff options
author | Alexey Brodkin <abrodkin@synopsys.com> | 2021-09-16 08:24:14 -0700 |
---|---|---|
committer | Chris Packham <judge.packham@gmail.com> | 2021-09-19 19:46:49 +1200 |
commit | 58c347c7819d8e400a79188d4cb3008c19451d3b (patch) | |
tree | aa9ac6bbafd7d083920d0cf2e042438bb03fe610 /packages/glibc/2.14.1/0006-dl-open-array-bounds.patch | |
parent | 7daa182506baf30adb35752369cf352ac2383c3b (diff) | |
download | crosstool-ng-58c347c7819d8e400a79188d4cb3008c19451d3b.tar.gz crosstool-ng-58c347c7819d8e400a79188d4cb3008c19451d3b.tar.bz2 crosstool-ng-58c347c7819d8e400a79188d4cb3008c19451d3b.zip |
gdb: Realy decouple building of native/target GDB & gdbserver
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>
Diffstat (limited to 'packages/glibc/2.14.1/0006-dl-open-array-bounds.patch')
0 files changed, 0 insertions, 0 deletions