From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: 37158@debbugs.gnu.org
Subject: bug#37158: 27.0.50; Build failure (MSYS2, master)
Date: Fri, 23 Aug 2019 16:05:02 +0300 [thread overview]
Message-ID: <83o90gjam9.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58oj2LfHSKk5e4Wc0n=WDjtMTo3MqFoU8v+_HghYypnnsOg@mail.gmail.com> (message from Richard Copley on Fri, 23 Aug 2019 13:44:22 +0100)
> From: Richard Copley <rcopley@gmail.com>
> Date: Fri, 23 Aug 2019 13:44:22 +0100
>
> The immediate problem should be fixed now, but what worries me is how
> on earth did your MinGW build ended up compiling the
> !HAVE_GAI_STRERROR branch? This shouldn't happen, by virtue of this
> part of nt/mingw-cfg.site:
>
> ac_cv_func_gai_strerror=yes
>
> Doesn't your src/config.h has this line:
>
> #define HAVE_GAI_STRERROR 1
>
> ? If not, we should find out why.
>
> Yes, that line is there, but also, in nt/ms-w32.h, there is this:
>
> /* Unlike MS and mingw.org, MinGW64 doesn't define gai_strerror as an
> inline function in a system header file, and instead seems to
> require to link against ws2_32.a. But we don't want to link with
> -lws2_32, as that would make Emacs dependent on the respective DLL.
> So MinGW64 is amply punished here by the following: */
> #undef HAVE_GAI_STRERROR
Ah, okay. It's clear now.
next prev parent reply other threads:[~2019-08-23 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 11:50 bug#37158: 27.0.50; Build failure (MSYS2, master) Richard Copley
2019-08-23 12:28 ` Robert Pluim
2019-08-23 12:40 ` Richard Copley
2019-08-23 12:35 ` Eli Zaretskii
[not found] ` <CAPM58oj2LfHSKk5e4Wc0n=WDjtMTo3MqFoU8v+_HghYypnnsOg@mail.gmail.com>
2019-08-23 13:05 ` Eli Zaretskii [this message]
2019-08-23 13:13 ` Richard Copley
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=83o90gjam9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37158@debbugs.gnu.org \
--cc=rcopley@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.