unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Nicolas Petton <nicolas@petton.fr>,
	nickleeh@foxmail.com, 20851@debbugs.gnu.org
Subject: bug#20851: 24.5; No 64-bit Emacs for Windows while the manual said there is.
Date: Fri, 19 Jun 2015 23:21:55 +0200	[thread overview]
Message-ID: <CAH8Pv0jdxv3mUqSxrMdeqAAu3_LRe+=U6hPHZnVtKk06=NFdDg@mail.gmail.com> (raw)
In-Reply-To: <83lhffjutp.fsf@gnu.org>

On Fri, Jun 19, 2015 at 10:40 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Nicolas Petton <nicolas@petton.fr>
>> Cc: Nick <nickleeh@foxmail.com>, 20851@debbugs.gnu.org
>> Date: Fri, 19 Jun 2015 22:20:13 +0200
>>
>> While I'm really bad at anything Windows-related, I could fire up a VM
>> and build Emacs 24.5, provided that there are some Windows-specific
>> instructions somewhere.
>
> The instructions are in nt/INSTALL.

?? But that file only refers to the MinGW project, which AFAIK does
not (yet?) provides support for 64-bit executables.

BTW, I also wouldn't mind to build & upload a 64-bit binary package for
MS-Windows, but so far, I've not found a "suitable" way of doing it.

I tried MSYS2.  It comes with a pretty convenient package manager
(pacman) and a good catalog of packages.  So I easily managed to
make a suitable build environment and then a 64-bit Emacs with support
for Images, GnuTLS, XML, etc.

But I found a problem: the GCC that comes with MSYS2 (from the
MinGW-w64 project) is configured for posix threads (instead of native
w32 threads).  Therefore, the runtime environment for that Emacs would
have this requirements:

1. "libwinpthread-1.dll" should be on PATH.
2. The runtime libraries used by Emacs should be configured for posix
threads too.

So, I'd prefer to make a "w32-threads" build, to get rid of that extra
dependency.  But I still haven't found a convenient way of doing that.
(I must admit that this is not among my current priorities, though)

-- 
Dani Moncayo





  parent reply	other threads:[~2015-06-19 21:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 16:23 bug#20851: 24.5; No 64-bit Emacs for Windows while the manual said there is Nick 
2015-06-19 17:33 ` Eli Zaretskii
2015-06-19 20:10   ` Stefan Monnier
2015-06-19 20:20     ` Nicolas Petton
2015-06-19 20:40       ` Eli Zaretskii
2015-06-19 20:45         ` Nicolas Petton
2015-06-20  6:45           ` Eli Zaretskii
2015-06-20 18:24             ` Glenn Morris
2015-06-21 15:12               ` Eli Zaretskii
2015-06-19 21:21         ` Dani Moncayo [this message]
2015-06-20  6:48           ` Eli Zaretskii
2015-06-19 20:40     ` Eli Zaretskii
2015-06-20 18:29       ` Glenn Morris
2015-06-22  7:04     ` Glenn Morris
2015-06-20 10:39   ` Nick 

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='CAH8Pv0jdxv3mUqSxrMdeqAAu3_LRe+=U6hPHZnVtKk06=NFdDg@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=20851@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=nickleeh@foxmail.com \
    --cc=nicolas@petton.fr \
    /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).