From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Windows emacs-25.1 i686 vs x86_64?
Date: Thu, 3 Nov 2016 16:39:51 +0100 [thread overview]
Message-ID: <20161103153951.GC3516@tuxteam.de> (raw)
In-Reply-To: <6e2cffe5-942b-48d4-9ed5-ef39803bcd30@googlegroups.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Nov 03, 2016 at 08:32:40AM -0700, David M. Miller wrote:
> When I went to download 25.1 for windows I saw two packages on the main GNU ftp server:
>
> emacs-25.1-i686-w64-mingw32.zip
> - AND -
> emacs-25.1-x86_64-w64-mingw32.zip
>
> but no explanation of the difference between them in the README file.
>
> Also, there seems to be a separate package of "deps" for each:
>
> emacs-25-i686-deps.zip
> - AND -
> emacs-25-x86_64-deps.zip
>
> the need for which is also not explained anywhere (dependencies? dependencies for what?).
>
> Does anyone know what the difference between the i686 and x86_64 packages are?
> Does anyone know what the "deps" packages are for?
Not exactly correct, but good enough: you want 686 if you have a 32 bit
system (that'd include a 32 bit Windows running on 64 bit hardware, I
guess). You want 86_64 if you are on a 64 bit system.
This all assuming you are on Intel or AMD hardware (does Windows run on
anything else?)
regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlgbWkcACgkQBcgs9XrR2kYWsQCeNIelbd5hWnUrVUBzk45qhDvj
R4MAn2N89KPYXBtKz0HuOqNCKC3CCCOD
=MEv1
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-11-03 15:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 15:32 Windows emacs-25.1 i686 vs x86_64? David M. Miller
2016-11-03 15:39 ` tomas [this message]
2016-11-03 16:00 ` David M. Miller
2016-11-03 16:26 ` John Mastro
2016-11-03 16:28 ` Phillip Lord
2016-11-03 17:44 ` David M. Miller
2016-11-03 22:21 ` Phillip Lord
2016-11-03 17:58 ` Eli Zaretskii
2016-11-03 22:25 ` Phillip Lord
2016-11-04 7:19 ` Eli Zaretskii
2016-11-04 10:19 ` Phillip Lord
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=20161103153951.GC3516@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@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.
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).