Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Change boolean options to bool instead of int
Date: Tue, 17 Sep 2019 05:03:00 -0000	[thread overview]
Message-ID: <CAPTJ0XGjTcm=wFZJjOw84CuGYhAtE7-jayK5XDKu7O0Gt3uqZQ@mail.gmail.com> (raw)
In-Reply-To: <CAPTJ0XHLk9hPdPpdeXMsi87wdvyZmNV54i9kZ-tw0VkLyKNh4w@mail.gmail.com>

On Tue, Sep 17, 2019 at 12:23 PM Christian Biesinger
<cbiesinger@google.com> wrote:
>
> On Tue, Sep 17, 2019 at 3:02 AM Simon Marchi <simark@simark.ca> wrote:
> > This also reminded me that there are some uses of add_setshow_boolean_cmd in native files.
> > Doing a
> >
> >   grep add_setshow_boolean_cmd *-nat.c
> >
> > to find them would be a good start, but actually all the files listed in configure.nat should
> > be considered, as they may not be included in your build.
> >
> > For those native files, you can try to build test some if you want to, but you probably won't
> > be able to build all of them.  That is fine, just do a best effort of changing the spots you
> > find.
>
> I wasn't able to build any of them (as "make -C obj/gdb
> mips-linux-nat.o, etc.). But I did update what I could. I did also go
> through the other files in configure.nat and changed what I could
> find.
>
> (note that some of the *-nat.c files are referencing show_debug_regs
> which is in a common file, so they didn't need changing)

Per advice from Simon on IRC, I successfully crosscompiled the latest
version of the patch to these targets:
arm-linux-gnueabihf, mips-linux-gnu, powerpc-linux-gnu,
s390x-linux-gnu, x86_64-w64-mingw32

I don't have a way to compile for darwin, fbsd, obsd, gnu, I think.

Christian


Christian


  parent reply	other threads:[~2019-09-17  5:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-15  8:34 [RFC] " Christian Biesinger via gdb-patches
2019-09-15 23:10 ` Simon Marchi
2019-09-16  0:22   ` Christian Biesinger via gdb-patches
2019-09-16 17:06     ` Simon Marchi
2019-09-15 23:29 ` Andrew Burgess
2019-09-16  3:09   ` Christian Biesinger via gdb-patches
2019-09-16  3:10     ` [PATCH v2] " Christian Biesinger via gdb-patches
2019-09-16 17:32       ` Andrew Burgess
2019-09-16 18:03       ` Simon Marchi
2019-09-17  3:23         ` Christian Biesinger via gdb-patches
2019-09-17  3:26           ` [PATCH v3] " Christian Biesinger via gdb-patches
2019-09-17 12:43             ` Simon Marchi
2019-09-18  0:34               ` [PATCH v4] " Christian Biesinger via gdb-patches
2019-09-17  5:03           ` Christian Biesinger via gdb-patches [this message]
2019-09-16 17:04   ` [PP?] Re: [RFC] " Simon Marchi

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='CAPTJ0XGjTcm=wFZJjOw84CuGYhAtE7-jayK5XDKu7O0Gt3uqZQ@mail.gmail.com' \
    --to=gdb-patches@sourceware.org \
    --cc=cbiesinger@google.com \
    --cc=simark@simark.ca \
    /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