From: Simon Marchi <simark@simark.ca>
To: Daniel Xu <dxu@dxuuu.xyz>, "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH V3 0/3] eBPF support
Date: Sat, 4 Jul 2020 23:20:23 -0400 [thread overview]
Message-ID: <16a86d50-b34d-13cf-7a6b-32d9db6b5450@simark.ca> (raw)
In-Reply-To: <C3YD1C9NK7XW.3T15LTZXO95LX@maharaja>
On 2020-07-04 11:12 p.m., Daniel Xu wrote:
> Sorry if this is a silly question, but how do I build `sim` support into
> gdb?
>
> I've tried running the following against the top-level configure script:
>
> ```
> $ ../configure --enable-sim --enable-unit-tests --enable-maintainer-mode
> $ make -j4
> $ make -C gdb run
> make: Entering directory '/home/daniel/dev/gdb/build/gdb'
> [...]
>
> (gdb) target sim
> Undefined target command: "sim". Try "help target".
The sim is built when GDB & co are configured with a suitable --target (a target for
which there is a sim). If you look at Jose's patches, they modify the configure.tgt
files of gdb/ and sim/ to recognize target triplets of the form `bpf-*-*`. According
to this:
https://lwn.net/Articles/800606/
the triplet to use is `bpf-unknown-none` (and there's even a nice picture!). So, try
adding `--target=bpf-unknown-none` to your configure line.
Simon
next prev parent reply other threads:[~2020-07-05 3:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 12:46 Jose E. Marchesi
2020-07-03 12:46 ` [PATCH V3 1/3] gdb: support for eBPF Jose E. Marchesi
2020-07-03 12:46 ` [PATCH V3 2/3] sim: eBPF simulator Jose E. Marchesi
2020-07-03 12:46 ` [PATCH V3 3/3] sim: generated files for the " Jose E. Marchesi
2020-07-03 20:37 ` [PATCH V3 0/3] eBPF support Daniel Xu
2020-07-05 0:27 ` Jose E. Marchesi
2020-07-05 1:34 ` Simon Marchi
2020-07-05 3:12 ` Daniel Xu
2020-07-05 3:20 ` Simon Marchi [this message]
2020-07-05 10:18 ` Jose E. Marchesi
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=16a86d50-b34d-13cf-7a6b-32d9db6b5450@simark.ca \
--to=simark@simark.ca \
--cc=dxu@dxuuu.xyz \
--cc=gdb-patches@sourceware.org \
--cc=jose.marchesi@oracle.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