From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [w32] Build failure on master (pthread_sigmask.h)
Date: Fri, 31 May 2019 12:18:02 +0300 [thread overview]
Message-ID: <83tvdbvv79.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58ogp1w+8B_w3jNFb8-Btc=CVfYA5O2nv4iz_yz4pCY15+w@mail.gmail.com> (message from Richard Copley on Thu, 30 May 2019 20:39:30 +0100)
> From: Richard Copley <rcopley@gmail.com>
> Date: Thu, 30 May 2019 20:39:30 +0100
> Cc: Emacs Development <emacs-devel@gnu.org>
>
> gl_cv_func_pthread_sigmask_macro=no
>
> Yes, that works. (The build succeeds and no pthread_sigmask.o is generated.)
Thanks for testing, pushed.
> I'm impressed, thanks.
There's no magic: I looked into my config.log and saw that the above
variable was set to "no" because I didn't have pthreads.h.
> (On my box the problem doesn't happen because I don't have the
> pthread.h header polluting my system.)
>
> One package's pollution is another's prerequisite. Easily eradicated:
>
> pacman -R ${MINGW_PACKAGE_PREFIX}-libwinpthread-git
Right. FWIW, I've decided long ago that the trouble produced by
having pthreads headers and import libraries installed was way greater
than any advantages it gives. The Windows ports of pthreads are
simply not reliable enough, IME.
prev parent reply other threads:[~2019-05-31 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 13:04 [w32] Build failure on master (pthread_sigmask.h) Richard Copley
2019-05-30 14:12 ` Eli Zaretskii
2019-05-30 15:54 ` Richard Copley
2019-05-30 18:44 ` Eli Zaretskii
2019-05-30 19:39 ` Richard Copley
2019-05-31 9:18 ` Eli Zaretskii [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=83tvdbvv79.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@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.