From: LIU Hao <lh_mouse@126.com>
To: Achim Gratz <Stromeko@nexgo.de>, gcc@gcc.gnu.org
Subject: Re: gcc-12.3 cannot build gcc-ada on Cygwin
Date: Wed, 24 May 2023 09:42:56 +0800 [thread overview]
Message-ID: <e3b16b5b-a13b-f37b-b913-3c3ecb1fbcf9@126.com> (raw)
In-Reply-To: <874jo49ljg.fsf@Rainer.invalid>
[-- Attachment #1.1: Type: text/plain, Size: 530 bytes --]
在 2023/5/23 04:08, Achim Gratz 写道:
> I've backported the patch _and_ defined both WIN32_LEAN_AND_MEAN and
> COM_NO_WINDOWS_H (of which I find no reference anywhere in the sources,
> so it's probably doing something in the Windows headers?) and the build
> has been working through stage 3.
That look likes a private macro that prevents inclusion of 'msxml.h', which can identified by
examining Windows headers. It's undocumented and probably shouldn't be defined by users.
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-05-24 1:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 16:35 Achim Gratz
2023-05-21 18:12 ` LIU Hao
2023-05-22 20:08 ` Achim Gratz
2023-05-24 1:42 ` LIU Hao [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=e3b16b5b-a13b-f37b-b913-3c3ecb1fbcf9@126.com \
--to=lh_mouse@126.com \
--cc=Stromeko@nexgo.de \
--cc=gcc@gcc.gnu.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).