public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Enze Li <enze.li@hotmail.com>, gdb-patches@sourceware.org
Cc: enze.li@gmx.com
Subject: Re: [PATCH] gdb/netbsd: add missing header file
Date: Sun, 24 Jul 2022 21:01:11 -0400	[thread overview]
Message-ID: <96a2fc09-113a-887c-c458-72568967b78a@simark.ca> (raw)
In-Reply-To: <OS3P286MB2152A2E70ACEA4A1ED888D74F0929@OS3P286MB2152.JPNP286.PROD.OUTLOOK.COM>



On 2022-07-23 22:55, Enze Li via Gdb-patches wrote:
> I ran into this error when building GDB on NetBSD:
> 
>   CXX    netbsd-nat.o
> netbsd-nat.c: In member function 'virtual bool nbsd_nat_target::info_proc(const char*, info_proc_what)':
> netbsd-nat.c:314:3: error: 'gdb_argv' was not declared in this scope
>    gdb_argv built_argv (args);
>    ^~~~~~~~
> netbsd-nat.c:314:3: note: suggested alternative: 'gdbarch'
>    gdb_argv built_argv (args);
>    ^~~~~~~~
>    gdbarch
> netbsd-nat.c:315:7: error: 'built_argv' was not declared in this scope
>    if (built_argv.count () == 0)
>        ^~~~~~~~~~
> netbsd-nat.c:315:7: note: suggested alternative: 'buildargv'
>    if (built_argv.count () == 0)
>        ^~~~~~~~~~
>        buildargv
> gmake[2]: *** [Makefile:1893: netbsd-nat.o] Error 1
> 
> Fix this by adding the missing header file, as it is obvious.
> 
> Tested by rebuilding on NetBSD/amd64.
> ---
>  gdb/netbsd-nat.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/gdb/netbsd-nat.c b/gdb/netbsd-nat.c
> index c45df391afc..8a4a43270d6 100644
> --- a/gdb/netbsd-nat.c
> +++ b/gdb/netbsd-nat.c
> @@ -25,6 +25,7 @@
>  #include "netbsd-tdep.h"
>  #include "inferior.h"
>  #include "gdbarch.h"
> +#include "gdbsupport/buildargv.h"
>  
>  #include <sys/types.h>
>  #include <sys/ptrace.h>

LGTM.

Simon

  reply	other threads:[~2022-07-25  1:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-24  2:55 Enze Li
2022-07-25  1:01 ` Simon Marchi [this message]
2022-07-26 12:25   ` Enze Li

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=96a2fc09-113a-887c-c458-72568967b78a@simark.ca \
    --to=simark@simark.ca \
    --cc=enze.li@gmx.com \
    --cc=enze.li@hotmail.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).