From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 0/6] Move gdbsupport to top level
Date: Thu, 16 Jan 2020 04:23:00 -0000 [thread overview]
Message-ID: <5a9d5f71-aecd-8151-c8cd-174affb3aaf3@simark.ca> (raw)
In-Reply-To: <20200109005807.7314-1-tom@tromey.com>
On 2020-01-08 7:58 p.m., Tom Tromey wrote:
> Here is an update of the series to move gdbsupport to the top level.
> This is one step in the bigger projecct to move gdbserver to top
> level.
>
> In this patch, gdbsupport is given its own configure script --
> however, gdbserver still builds its own copy. gdb and gdbserver won't
> share a gdbsupport library until the final series.
>
> This version of the patch fixes up the problems that Pedro pointed out
> in the shared nat/ and target/ code. In particular, now they can
> simply rely on the shared config.h. This is enforced by ensuring that
> the necessary defines are all available; the checker script I used to
> find the issues is provided in patch #5.
>
> I wasn't able to send this through the buildbot. I did test it on
> x86-64 Fedora 29. I also build it using a mingw cross.
>
> If you want to try it, it is on the branch
> submit/move-gdbsupport-to-top in my github.
>
> Let me know what you think.
>
> Tom
Hi Tom,
I think we are missing a dependency of the gdbsupport directory on the bfd
directory. In a build from scratch, try to do "make all-gdbsupport". You
should get:
make[2]: Entering directory '/home/simark/build/binutils-gdb/gdbsupport'
CC agent.o
In file included from /home/simark/src/binutils-gdb/gdbsupport/common-defs.h:109,
from /home/simark/src/binutils-gdb/gdbsupport/agent.c:20:
/home/simark/src/binutils-gdb/gdbsupport/common-types.h:35:10: fatal error: bfd.h: No such file or directory
35 | #include "bfd.h"
| ^~~~~~~
Note that on my development machine, I didn't see this problem at first, but
then I realized that it was including /usr/include/bfd.h. After I deleted it,
I got the error.
In the top-level Makefile, gdbsupport currently depends on configure-bfd. I
suppose it should depend on all-bfd, since it needs for bfd.h to be generated?
Simon
prev parent reply other threads:[~2020-01-16 2:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 0:58 Tom Tromey
2020-01-09 0:58 ` [PATCH v2 5/6] Add gdbsupport check-defines script Tom Tromey
2020-01-09 0:58 ` [PATCH v2 1/6] Consolidate definition of USE_WIN32API Tom Tromey
2020-01-09 0:58 ` [PATCH v2 4/6] Remove use of <config.h> from gdb/nat/ Tom Tromey
2020-01-09 0:58 ` [PATCH v2 6/6] Don't link gdb twice against libiberty Tom Tromey
2020-01-11 16:58 ` [PATCH v2 0/6] Move gdbsupport to top level Tom Tromey
2020-01-12 2:48 ` Simon Marchi
2020-01-14 23:25 ` Tom Tromey
2020-01-15 0:36 ` Tom Tromey
2020-01-15 21:27 ` Christian Biesinger via gdb-patches
2020-01-17 18:02 ` Tom Tromey
2020-01-15 14:30 ` Pedro Alves
[not found] ` <8a8de6a9-37b8-cad3-c818-be903037fe48@redhat.com>
2020-01-15 16:07 ` Pedro Alves
[not found] ` <87c733a2-2b25-a954-88a1-9bfb1a7eca12@redhat.com>
2020-01-15 21:46 ` Pedro Alves
2020-01-15 22:12 ` Pedro Alves
2020-01-16 0:48 ` Pedro Alves
2020-01-16 2:57 ` Christian Biesinger via gdb-patches
2020-01-16 17:22 ` Pedro Alves
2020-01-16 18:01 ` Christian Biesinger via gdb-patches
2020-01-16 18:28 ` Pedro Alves
2020-01-16 19:21 ` Christian Biesinger via gdb-patches
2020-01-16 9:02 ` Simon Marchi
2020-01-16 15:24 ` Pedro Alves
2020-01-17 12:20 ` Simon Marchi
2020-01-17 13:37 ` Pedro Alves
2020-01-17 14:40 ` Simon Marchi
2020-01-17 15:32 ` Pedro Alves
2020-01-17 18:13 ` Tom Tromey
2020-01-16 4:23 ` Simon Marchi [this message]
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=5a9d5f71-aecd-8151-c8cd-174affb3aaf3@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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