From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: Re: [master b3cf281] Unbreak the MinGW build
Date: Fri, 16 Dec 2016 16:16:44 -0600 [thread overview]
Message-ID: <861sx7a59v.fsf@stephe-leake.org> (raw)
In-Reply-To: <83eg1887q4.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 16 Dec 2016 12:54:27 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> I needed this commit to prevent temacs from crashing during dumping.
> Don't ask me how including errno.h (both the one from Gnulib and the
> MinGW one) could cause this, especially as the preprocessed __fpending
> doesn't seem to change a bit as result of that, and it doesn't seem to
> even be called during dumping. The facts are stubborn: if I leave
> that inclusion in place, I get a crash, removing it fixes the crash.
To help with this, I'm trying to build master on Mingw64, but I'm
missing some threads library (I assume due to the recent addition of
concurrency support):
gcc.exe: error: thread.o: No such file or directory
gcc.exe: error: systhread.o: No such file or directory
mingw has several "threads" libraries;
mingw64/mingw-w64-x86_64-npth 1.2-2
New portable threads library (mingw-w64)
mingw64/mingw-w64-x86_64-port-scanner 1.3-2
A multi threaded TCP port scanner from SecPoint.com (mingw-w64)
mingw64/mingw-w64-x86_64-winpthreads-git 5.0.0.4573.628fdbf-1 (mingw-w64-x86_64-toolchain) [installed]
MinGW-w64 winpthreads library
which one should I use?
--
-- Stephe
next prev parent reply other threads:[~2016-12-16 22:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 10:54 [master b3cf281] Unbreak the MinGW build Eli Zaretskii
2016-12-16 15:43 ` Paul Eggert
2016-12-16 18:11 ` Bruno Haible
2016-12-16 21:10 ` Eli Zaretskii
2016-12-16 23:17 ` Bruno Haible
2016-12-17 0:30 ` Paul Eggert
2016-12-17 7:51 ` Eli Zaretskii
2016-12-17 11:17 ` Eli Zaretskii
2016-12-16 22:16 ` Stephen Leake [this message]
2016-12-16 22:38 ` Stephen Leake
2016-12-17 7:40 ` 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=861sx7a59v.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).