public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "pexu at sourceware dot mail.kapsi.fi" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31307] New: gdb/symtab.h: SEARCH_ALL clashes with <winioctl.h> on MinGW Date: Mon, 29 Jan 2024 09:55:15 +0000 [thread overview] Message-ID: <bug-31307-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31307 Bug ID: 31307 Summary: gdb/symtab.h: SEARCH_ALL clashes with <winioctl.h> on MinGW Product: gdb Version: HEAD Status: UNCONFIRMED Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: pexu at sourceware dot mail.kapsi.fi Target Milestone: --- Hi. Recent domain_search_flags patch [1] introduces a convenience constant SEARCH_ALL that unfortunately clashes with SEARCH_ALL macro that is defined <winioctl.h>. This header file is included indirectly when compiling gdb/mingw-hdep.c (via gdb/serial.h:23 -> /mingw-w64/include/winsock2.h:23 -> /mingw-w64/include/windows.h:97 -> /mingw-w64/include/winscard.h:11 -> /mingw-w64/include/winioctl.h). A quick (and dirty) workaround would be to add #define NOCRYPT prior serial.h include. However, in the long run, it might be more beneficial to move <windows.h> et. al. to a shared header that sets up all feature removal macros. [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=25f31e1820dcec2f0c073c28cbf88646c7c2af97 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-01-29 9:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-29 9:55 pexu at sourceware dot mail.kapsi.fi [this message] 2024-01-29 13:24 ` [Bug gdb/31307] " tromey at sourceware dot org 2024-01-29 16:17 ` tromey at sourceware dot org 2024-01-29 16:41 ` tromey at sourceware dot org 2024-01-29 16:47 ` tromey at sourceware dot org 2024-02-01 14:23 ` cvs-commit at gcc dot gnu.org 2024-02-01 16:19 ` tromey at sourceware dot org
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=bug-31307-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).