From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, "Fabiano Rosas" <farosas@suse.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Laurent Vivier" <laurent@vivier.eu>
Subject: Re: [PATCH] gdbstub: Only build libgdb_user.fa / libgdb_softmmu.fa if necessary
Date: Wed, 29 Mar 2023 18:03:40 +0100 [thread overview]
Message-ID: <87bkkbqykt.fsf@linaro.org> (raw)
In-Reply-To: <20230329161852.84992-1-philmd@linaro.org>
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> It is pointless to build libgdb_user.fa in a system-only build
> (or libgdb_softmmu.fa in a user-only build). Besides, in some
> restricted build configurations, some APIs might be restricted /
> not available. Example in a KVM-only builds where TCG is disabled:
>
> $ ninja qemu-system-x86_64
> [99/2187] Compiling C object gdbstub/libgdb_user.fa.p/user.c.o
> FAILED: gdbstub/libgdb_user.fa.p/user.c.o
> ../../gdbstub/user.c: In function ‘gdb_breakpoint_insert’:
> ../../gdbstub/user.c:438:19: error: implicit declaration of function ‘cpu_breakpoint_insert’; did you mean ‘gdb_breakpoint_insert’? [-Werror=implicit-function-declaration]
> 438 | err = cpu_breakpoint_insert(cpu, addr, BP_GDB, NULL);
> | ^~~~~~~~~~~~~~~~~~~~~
> | gdb_breakpoint_insert
> ../../gdbstub/user.c:438:19: error: nested extern declaration of
> ‘cpu_breakpoint_insert’ [-Werror=nested-externs]
> ../../gdbstub/user.c: In function ‘gdb_breakpoint_remove’:
> ../../gdbstub/user.c:459:19: error: implicit declaration of function
> ‘cpu_breakpoint_remove’; did you mean ‘gdb_breakpoint_remove’?
> [-Werror=implicit-function-declaration]
> 459 | err = cpu_breakpoint_remove(cpu, addr, BP_GDB);
> | ^~~~~~~~~~~~~~~~~~~~~
> | gdb_breakpoint_remove
> ../../gdbstub/user.c:459:19: error: nested extern declaration of ‘cpu_breakpoint_remove’ [-Werror=nested-externs]
> cc1: all warnings being treated as errors
> ninja: build stopped: subcommand failed.
>
> Fixes: 61b2e136db ("gdbstub: only compile gdbstub twice for whole build")
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Queued to for-8.0/more-misc-fixes, thanks.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2023-03-29 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 16:18 [PATCH] gdbstub: Only build libgdb_user.fa / libgdb_softmmu.fa if necessary Philippe Mathieu-Daudé
2023-03-29 16:39 ` Richard Henderson
2023-03-29 17:03 ` Alex Bennée [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=87bkkbqykt.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=farosas@suse.de \
--cc=laurent@vivier.eu \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.