all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: 22959@debbugs.gnu.org
Subject: bug#22959: Emacs on Windows depends on libwinpthreads
Date: Wed, 09 Mar 2016 14:52:18 +0000	[thread overview]
Message-ID: <87egbj4sbh.fsf@russet.org.uk> (raw)



Currently, building Emacs under msys2/ming-w64 produces a binary that
depends on libwinpthread.dll. The practical upshot of this is that after
building and installing Emacs according to the instructions, Emacs
cannot be launched from the Windows explorer -- it can be run from msys2
which has the path set up correctly. A binary release will, therefore, fail.

Using the dependency walker shows the dependency is directly from Emacs,
and it appears to have come from a change in ming-w64, as reported here.

https://sourceforge.net/p/mingw-w64/mailman/message/31213279/

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748353

This affects emacs-25, master and, indeed, emacs-24 built using the
current tool chain.





             reply	other threads:[~2016-03-09 14:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 14:52 Phillip Lord [this message]
2016-03-09 16:20 ` bug#22959: Emacs on Windows depends on libwinpthreads Eli Zaretskii
2016-03-09 16:32   ` Phillip Lord
2016-03-09 16:59     ` Eli Zaretskii
2016-03-09 18:56       ` Phillip Lord
2016-03-09 19:16         ` Eli Zaretskii
2016-04-16 21:48 ` Fabrice Popineau
2016-04-17 14:37   ` Eli Zaretskii
2016-04-17 15:25     ` Fabrice Popineau
2016-04-17 16:42       ` Eli Zaretskii
2016-04-17 19:31         ` Fabrice Popineau
2016-04-18 18:58           ` Eli Zaretskii
2016-04-18 19:50             ` Fabrice Popineau
2016-04-21 16:25               ` Eli Zaretskii
2016-04-18 13:06     ` Phillip Lord
2016-04-18 13:41       ` Fabrice Popineau
2016-04-18 19:02         ` Eli Zaretskii
2016-04-19  7:26           ` Fabrice Popineau

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=87egbj4sbh.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=22959@debbugs.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 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.