From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 3/6] gdb: Add a dependency between gdb and libbacktrace
Date: Thu, 19 Aug 2021 10:49:28 +0100 [thread overview]
Message-ID: <0b8ebcf5d8b4867a9612420cb8546797b5407647.1629366146.git.andrew.burgess@embecosm.com> (raw)
In-Reply-To: <cover.1629366146.git.andrew.burgess@embecosm.com>
GDB is going to start using libbacktrace, so add a build dependency.
ChangeLog:
* Makefile.def: Add all-gdb dependency on all-libbacktrace.
* Makefile.in: Regenerate.
---
Makefile.def | 1 +
Makefile.in | 1 +
2 files changed, 2 insertions(+)
diff --git a/Makefile.def b/Makefile.def
index 5a460f1dbbc..d5b1ee882b6 100644
--- a/Makefile.def
+++ b/Makefile.def
@@ -408,6 +408,7 @@ dependencies = { module=all-gdb; on=all-sim; };
dependencies = { module=all-gdb; on=all-libdecnumber; };
dependencies = { module=all-gdb; on=all-libtermcap; };
dependencies = { module=all-gdb; on=all-libctf; };
+dependencies = { module=all-gdb; on=all-libbacktrace; };
// Host modules specific to gdbserver.
dependencies = { module=configure-gdbserver; on=all-gnulib; };
diff --git a/Makefile.in b/Makefile.in
index 9b3a5d75735..91b714f6e88 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -52534,6 +52534,7 @@ all-gdb: maybe-all-libiconv
all-gdb: maybe-all-opcodes
all-gdb: maybe-all-libdecnumber
all-gdb: maybe-all-libctf
+all-gdb: maybe-all-libbacktrace
all-gdbserver: maybe-all-libiberty
configure-gdbsupport: maybe-configure-intl
all-gdbsupport: maybe-all-intl
--
2.25.4
next prev parent reply other threads:[~2021-08-19 9:49 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 9:49 [PATCH 0/6] Display GDB backtrace for internal errors Andrew Burgess
2021-08-19 9:49 ` [PATCH 1/6] gdb: use bool instead of int in struct internal_problem Andrew Burgess
2021-08-19 18:33 ` Simon Marchi
2021-09-07 14:11 ` Andrew Burgess
2021-08-19 9:49 ` [PATCH 2/6] gdb: make use of std::string in utils.c Andrew Burgess
2021-08-19 18:41 ` Simon Marchi
2021-09-07 14:12 ` Andrew Burgess
2021-08-19 9:49 ` Andrew Burgess [this message]
2021-08-19 18:43 ` [PATCH 3/6] gdb: Add a dependency between gdb and libbacktrace Simon Marchi
2021-08-27 17:44 ` Tom Tromey
2021-08-30 20:33 ` Andrew Burgess
2021-08-19 9:49 ` [PATCH 4/6] Copy in libbacktrace from gcc Andrew Burgess
2021-08-27 17:46 ` Tom Tromey
2021-08-30 20:34 ` Andrew Burgess
2021-08-19 9:49 ` [PATCH 5/6] gdb: use libbacktrace to create a better backtrace for fatal signals Andrew Burgess
2021-08-19 18:58 ` Simon Marchi
2021-08-19 9:49 ` [PATCH 6/6] gdb: print backtrace for internal error/warning Andrew Burgess
2021-08-19 19:01 ` Simon Marchi
2021-08-30 14:16 ` [PATCH 0/6] Display GDB backtrace for internal errors Tom de Vries
2021-08-30 20:35 ` Andrew Burgess
2021-08-31 11:17 ` Florian Weimer
2021-09-28 11:26 ` [PUSHED " Andrew Burgess
2021-09-28 11:26 ` [PUSHED 1/6] top-level configure: setup target_configdirs based on repository Andrew Burgess
2021-09-28 11:26 ` [PUSHED 2/6] gdb: Add a dependency between gdb and libbacktrace Andrew Burgess
2021-09-28 11:26 ` [PUSHED 4/6] src-release.sh: add libbacktrace to GDB_SUPPORT_DIRS Andrew Burgess
2021-09-28 11:26 ` [PUSHED 5/6] gdb: use libbacktrace to create a better backtrace for fatal signals Andrew Burgess
2021-09-28 18:55 ` Pedro Alves
2021-09-29 8:21 ` Andrew Burgess
2021-09-29 3:09 ` Simon Marchi
2021-09-29 9:56 ` Andrew Burgess
2021-09-28 11:26 ` [PUSHED 6/6] gdb: print backtrace for internal error/warning Andrew Burgess
2021-09-28 12:26 ` Eli Zaretskii
2021-09-29 8:34 ` Andrew Burgess
2021-09-28 12:20 ` [PUSHED 3/6] Copy in libbacktrace from gcc Andrew Burgess
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0b8ebcf5d8b4867a9612420cb8546797b5407647.1629366146.git.andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).