unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: clang fails to compile emacs in Microsoft Windows
Date: Sat, 13 May 2023 09:00:33 +0300	[thread overview]
Message-ID: <83a5y8bwji.fsf@gnu.org> (raw)
In-Reply-To: <CALK-3mLSdvx8zuCzg0-_+7bgbZuvw0EA1pDHbGwcuarc5GT-dw@mail.gmail.com> (message from Biswapriyo Nath on Sat, 13 May 2023 01:40:11 +0530)

> From: Biswapriyo Nath <nathbappai@gmail.com>
> Date: Sat, 13 May 2023 01:40:11 +0530
> Cc: Óscar Fuentes <ofv@wanadoo.es>, eliz@gnu.org
> 
> Adding the wait() declaration in nt/inc/sys/wait.h fixes the issue.

That's not the right solution for this issue, though, IMO.  Adding
that declaration is only TRT if you also add some implementation of
'wait' to one of the w32*.c files.

The problem here is that the configure script rejects the sys/wait.h
header we provide for MS-Windows because it deduces it isn't
Posix-compliant enough.  That is the problem to fix: convince the
configure script that our sys/wait.h is fine (which it is, since it
does everything the MS-Windows build needs from it).  The right means
for doing so is the nt/mingw-cfg.site file, where you need to add

  ac_cv_header_sys_wait_h=yes

This will cause this test to succeed unconditionally, which is what we
need.



  reply	other threads:[~2023-05-13  6:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 14:11 clang fails to compile emacs in Microsoft Windows Biswapriyo Nath
2023-05-12 15:06 ` Eli Zaretskii
2023-05-12 15:47   ` Óscar Fuentes
2023-05-12 15:59     ` Biswapriyo Nath
2023-05-12 16:03       ` Biswapriyo Nath
2023-05-12 16:13       ` Eli Zaretskii
2023-05-12 16:10     ` Eli Zaretskii
2023-05-12 20:07       ` Óscar Fuentes
2023-05-12 20:10         ` Biswapriyo Nath
2023-05-13  6:00           ` Eli Zaretskii [this message]
2023-05-13  7:21             ` Biswapriyo Nath
2023-05-13  5:53         ` Eli Zaretskii
2023-05-13 12:39           ` Óscar Fuentes
2023-05-13 12:46             ` Eli Zaretskii

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=83a5y8bwji.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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).