Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Andrei Pikas <gdb@mail.api.win>, tom@tromey.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v8] Add an option with a color type.
Date: Mon, 3 Feb 2025 17:23:24 +0100	[thread overview]
Message-ID: <a73afabf-2c70-4b34-aeae-0f1a828a7197@suse.de> (raw)
In-Reply-To: <20241005192744.976782-1-gdb@mail.api.win>

On 10/5/24 21:27, Andrei Pikas wrote:
> +  int parsed_args = sscanf (*args, "#%2" SCNx8 "%2" SCNx8 "%2" SCNx8 "%n",
> +			    &r, &g, &b, &scanned_chars);

With an x86_64-w64-mingw32 targeted cross-build on x86_64-linux, I run into:
...
/data/vries/w/src/gdb/cli/cli-decode.c: In function 
'ui_file_style::color parse_cli_var_color(const char**)':
/data/vries/w/src/gdb/cli/cli-decode.c:2917:41: error: expected ')' 
before 'SCNx8'
  2917 |   int parsed_args = sscanf (*args, "#%2" SCNx8 "%2" SCNx8 "%2" 
SCNx8 "\
%n",
       |                            ~            ^~~~~~
       |                                         )
...

I tried adding an inttypes.h, but that didn't help.  It seems gnulib has:
...
./gnulib/import/inttypes.in.h:#if !defined SCNx8
./gnulib/import/inttypes.in.h:#  define SCNx8 "hhx"
...
which could help.

Thanks,
- Tom

  parent reply	other threads:[~2025-02-03 16:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 11:40 [PATCH v4] " Andrei Pikas
2022-10-16 13:45 ` Eli Zaretskii via Gdb-patches
2022-10-16 16:03   ` [PATCH v5] " Andrei Pikas
2022-10-16 16:22     ` Eli Zaretskii via Gdb-patches
2022-10-16 16:28       ` [PATCH v6] " Andrei Pikas
2022-10-16 16:45         ` Eli Zaretskii via Gdb-patches
2024-04-19 19:33         ` Tom Tromey
2024-04-19 19:52           ` Andrei Pikas
2024-04-19 20:19             ` Tom Tromey
2024-04-20 18:24               ` Tom Tromey
2024-04-20 18:32                 ` Andrei Pikas
2024-05-11 15:17                 ` Andrei Pikas
2024-05-13 19:02                   ` Tom Tromey
2024-05-21  9:00                     ` Andrei Pikas
2024-09-13 20:16         ` Tom Tromey
2024-09-14 18:06           ` Andrei Pikas
2024-09-14 19:38             ` Tom Tromey
2024-09-14 19:43               ` Andrei Pikas
2024-09-14 19:04           ` [PATCH v7] " Andrei Pikas
2024-09-15  5:37             ` Eli Zaretskii
2024-10-05 19:11               ` Andrei Pikas
2024-10-05 19:40                 ` Eli Zaretskii
2024-10-04 17:55             ` Tom Tromey
2024-10-05 17:55               ` Andrei Pikas
2024-10-05 19:27               ` [PATCH v8] " Andrei Pikas
2024-10-06  5:40                 ` Eli Zaretskii
2024-12-13 21:01                 ` Tom Tromey
2024-12-13 21:23                   ` Andrei Pikas
2024-12-14  7:59                     ` Eli Zaretskii
2025-01-12 20:34                     ` Tom Tromey
2025-02-03 16:23                 ` Tom de Vries [this message]
2025-02-04  0:24                   ` Tom Tromey
2025-02-04 14:24                     ` Tom de Vries

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=a73afabf-2c70-4b34-aeae-0f1a828a7197@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@mail.api.win \
    --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