| Message ID | 20210830202154.401688-1-andrew.burgess@embecosm.com |
|---|---|
| State | New |
| Headers | show |
| Series | gdb: Add a dependency between gdb and libbacktrace | expand |
On Mon, Aug 30, 2021 at 10:22 PM Andrew Burgess <andrew.burgess@embecosm.com> wrote: > > I plan to make use of libbacktrace within GDB. I believe that the > patch below needs to be merged into GCCs toplevel directory and then > back-ported to the binutils-gdb repository. > > Is this OK to merge? OK. > Thanks, > Andrew > > --- > > GDB is going to start using libbacktrace, so add a build dependency > between the two projects. This change needs to be added into the GCC > toplevel files, and then back-ported to the binutils-gdb repository. > > ChangeLog: > > * Makefile.def: Add all-gdb dependency on all-libbacktrace. > * Makefile.in: Regenerate. > --- > ChangeLog | 5 +++++ > Makefile.def | 1 + > Makefile.in | 1 + > 3 files changed, 7 insertions(+) > > diff --git a/Makefile.def b/Makefile.def > index fbfdb6fee08..de3e0052106 100644 > --- a/Makefile.def > +++ b/Makefile.def > @@ -423,6 +423,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 5c85fcc5dd0..61af99dc75a 100644 > --- a/Makefile.in > +++ b/Makefile.in > @@ -61237,6 +61237,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 >
diff --git a/Makefile.def b/Makefile.def index fbfdb6fee08..de3e0052106 100644 --- a/Makefile.def +++ b/Makefile.def @@ -423,6 +423,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 5c85fcc5dd0..61af99dc75a 100644 --- a/Makefile.in +++ b/Makefile.in @@ -61237,6 +61237,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
I plan to make use of libbacktrace within GDB. I believe that the patch below needs to be merged into GCCs toplevel directory and then back-ported to the binutils-gdb repository. Is this OK to merge? Thanks, Andrew --- GDB is going to start using libbacktrace, so add a build dependency between the two projects. This change needs to be added into the GCC toplevel files, and then back-ported to the binutils-gdb repository. ChangeLog: * Makefile.def: Add all-gdb dependency on all-libbacktrace. * Makefile.in: Regenerate. --- ChangeLog | 5 +++++ Makefile.def | 1 + Makefile.in | 1 + 3 files changed, 7 insertions(+)