unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Corwin Brust <corwin@bru.st>
To: Tak Ota <takaaki.ota@gmail.com>
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:36:14 -0500	[thread overview]
Message-ID: <CAJf-WoQ=y-Ov76HnOy8cWcPb-ohP6dUKpr6vRCFhrhvrqiy71A@mail.gmail.com> (raw)
In-Reply-To: <CACehZKLbU5x8Bcy1KUfH8ioq3FS8yy6GK0SCDbYP=f_9d+W-6g@mail.gmail.com>

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!





  reply	other threads:[~2023-04-12 16:36 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 [this message]
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
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='CAJf-WoQ=y-Ov76HnOy8cWcPb-ohP6dUKpr6vRCFhrhvrqiy71A@mail.gmail.com' \
    --to=corwin@bru.st \
    --cc=62792@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=takaaki.ota@gmail.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. 
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).