aboutsummaryrefslogtreecommitdiff
path: root/ltgcc.m4
diff options
context:
space:
mode:
authorAndrew Burgess <andrew.burgess@embecosm.com>2021-08-12 10:14:50 +0100
committerAndrew Burgess <andrew.burgess@embecosm.com>2021-09-28 12:21:21 +0100
commit63a4b10683992ae6ae2d93711369bc10df8fbce9 (patch)
tree20dc03cda5cf230928b0e53766f7245baf3ae0e6 /ltgcc.m4
parentfbe3443dcfbc9fc47394a171ec7bd5a9f7a7231c (diff)
downloadgdb-63a4b10683992ae6ae2d93711369bc10df8fbce9.zip
gdb-63a4b10683992ae6ae2d93711369bc10df8fbce9.tar.gz
gdb-63a4b10683992ae6ae2d93711369bc10df8fbce9.tar.bz2
Copy in libbacktrace from gcc
This copies in libbacktrace from the gcc repository as it was in the commit 62e420293a293608f383d9b9c7f2debd666e9fc9. GDB is going to start using this library soon. A dependency between GDB and libbacktrace has already been added to the top level Makefile, so, after this commit, when building GDB, libbacktrace will be built first. However, libbacktrace is not yet linked into GDB, or used by GDB in any way. It is possible to stop libbacktrace being built by configuring the tree with --disable-libbacktrace. This commit does NOT update src-release.sh, that will be done in the next commit, this commit ONLY imports libbacktrace from gcc. This means that if you try to make a release of GDB from exactly this commit then the release tar file will not include libbacktrace. However, as libbacktrace is an optional dependency this is fine.
Diffstat (limited to 'ltgcc.m4')
0 files changed, 0 insertions, 0 deletions