From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: 22959@debbugs.gnu.org
Subject: bug#22959: Emacs on Windows depends on libwinpthreads
Date: Wed, 09 Mar 2016 21:16:08 +0200 [thread overview]
Message-ID: <83h9gfo41z.fsf@gnu.org> (raw)
In-Reply-To: <87mvq7mqe2.fsf@russet.org.uk> (phillip.lord@russet.org.uk)
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Cc: 22959@debbugs.gnu.org
> Date: Wed, 09 Mar 2016 18:56:37 +0000
>
> >> The other solution is
> >>
> >> ./configure CFLAGS=-static
> >
> > If that gives reasonable results, yes. What problems, if any, does it
> > create?
>
> Well, it works, which is a reasonable result.
>
> Disadvantage? I guess, if it is dropped into an existing ming-w64
> installation, then it will (effectively) duplicate the libwinpthread
> binary that is there. More, it will not gain any updates to that
> libwinpthread library. If Emacs is being used standalone on a system
> with no other part of mingw/msys then these points are moot.
If that's the only problem, then I'd say go for it.
next prev parent reply other threads:[~2016-03-09 19:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 14:52 bug#22959: Emacs on Windows depends on libwinpthreads Phillip Lord
2016-03-09 16:20 ` 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 [this message]
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=83h9gfo41z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22959@debbugs.gnu.org \
--cc=phillip.lord@russet.org.uk \
/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.