From: Tak Ota <takaaki.ota@gmail.com>
To: Corwin Brust <corwin@bru.st>
Cc: 62792@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#62792: Emacs 29.0.90 build fails
Date: Wed, 12 Apr 2023 11:48:48 -0700 [thread overview]
Message-ID: <CACehZKJFRQTgrE117t8xMLa-bgFS6H_J0tN8jq8HYOguLCxznw@mail.gmail.com> (raw)
In-Reply-To: <CACehZKJ01Nu6eX2yj93fva0Vrv62QVytLOmyU0V4M9R_X47DRA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]
I am curious. What is the reason the next was added to w32.c?
#if _WIN32_WINNT < 0x0501
typedef struct
{
DWORD nFont;
COORD dwFontSize;
} CONSOLE_FONT_INFO;
#endif
This was not in the previous emacs source w32.c.
-Tak
On Wed, Apr 12, 2023 at 11:36 AM Tak Ota <takaaki.ota@gmail.com> wrote:
> Hi Corwin,
>
> ota@Tak-Dell-XPS15 /c/d/pub/emacs/emacs-29.0.90
> $ uname -a
> MINGW32_NT-6.2 TAK-DELL-XPS15 1.0.19(0.48/3/2) 2016-07-13 17:45 i686 Msys
>
> On Wed, Apr 12, 2023 at 9:36 AM Corwin Brust <corwin@bru.st> wrote:
>
>> Hi Tak,
>>
>> On Wed, Apr 12, 2023 at 11:18 AM Tak Ota <takaaki.ota@gmail.com> wrote:
>> >
>> > This is what I saw.
>>
>> Thanks for the error message detail. Unfortunately, I'm still not
>> able to reproduce this error. I'm building the emacs-29 branch under
>> MINGW32, in case that might be it. (It has been several days since I
>> tried x32 build.)
>>
>> Are you building from a git checkout or starting from the 29.0.90
>> source archive?
>>
>> Can you share the output from running "uname -a" in the shell where
>> you are building? Here's mine, for reference:
>>
>> MINGW64_NT-10.0-19043 Avalon 3.3.4-341.x86_64 2022-02-15 17:24 UTC
>> x86_64 Msys
>>
>> Finally, can you answer Eli's question below?
>>
>> >>
>> >> Also, which flavor of MinGW and which version are you using? The
>> >> above should be only visible with _WIN32_WINNT that is smaller than
>> >> 0x0501, which should not happen with latest MinGW64. And looking at
>> >> the latest MinGW64 headers, I see the definition of CONSOLE_FONT_INFO
>> >> structure there that is identical to the above, so how can it
>> >> conflict?
>>
>> Thanks for reporting!
>>
>
[-- Attachment #2: Type: text/html, Size: 2581 bytes --]
next prev parent reply other threads:[~2023-04-12 18:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 18:16 bug#62792: Emacs 29.0.90 build fails Tak Ota
2023-04-12 15:33 ` Eli Zaretskii
2023-04-12 16:18 ` Tak Ota
2023-04-12 16:36 ` Corwin Brust
2023-04-12 18:36 ` Tak Ota
2023-04-12 18:42 ` Tak Ota
2023-04-12 19:01 ` Eli Zaretskii
2023-04-12 18:48 ` Tak Ota [this message]
2023-04-12 18:59 ` Eli Zaretskii
2023-04-12 19:56 ` Tak Ota
2023-04-12 16:37 ` Eli Zaretskii
2023-04-12 17:44 ` Eli Zaretskii
2023-04-12 18:45 ` Tak Ota
2023-04-12 18:57 ` Eli Zaretskii
2023-04-12 19:54 ` Tak Ota
2023-04-13 5:20 ` Eli Zaretskii
2023-04-13 16:17 ` Tak Ota
2023-04-12 18:16 ` Tak Ota
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACehZKJFRQTgrE117t8xMLa-bgFS6H_J0tN8jq8HYOguLCxznw@mail.gmail.com \
--to=takaaki.ota@gmail.com \
--cc=62792@debbugs.gnu.org \
--cc=corwin@bru.st \
--cc=eliz@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).