From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Installing the current emacs-28 branch under Windows 10
Date: Mon, 18 Oct 2021 22:34:37 +0200 [thread overview]
Message-ID: <87y26qkr6q.fsf@telefonica.net> (raw)
In-Reply-To: xm46ilxurszd.fsf@duenenhof-wilhelm.de
"H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de> writes:
> I also tried to compile hunspell myself and was astonished that
> ./configure didn't work under the MinGW32 shell only under MinGW64!
> Only then I had a closer look and realised that my Emacs compilation
> says "x86_64-w64-mingw32". I'm thoroughly confused, it was compiled
> under the MinGW64 shell and now it says -mingw32? Is the Emacs
> executable a 64 bit program or 32 bit which is running on a x86_64
> architecture?
It is normal you are confused, the naming around MinGW is a mess, and
even worse if you add MSYS2.
In this case mingw32 simply means MinGW, which comes from the "old"
MinGW32 project (as it was originally named) and applies too to the
"new" MinGW-w64, w64 means the MinGW-w64 runtime and x86_64 is the
hardware architecture.
next prev parent reply other threads:[~2021-10-18 20:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 9:23 Installing the current emacs-28 branch under Windows 10 H. Dieter Wilhelm
2021-10-12 14:06 ` Eli Zaretskii
2021-10-12 18:02 ` H. Dieter Wilhelm
2021-10-12 18:59 ` Eli Zaretskii
2021-10-13 20:30 ` H. Dieter Wilhelm
2021-10-13 21:28 ` Óscar Fuentes
2021-10-14 6:45 ` Eli Zaretskii
2021-10-17 23:01 ` Óscar Fuentes
2021-10-17 23:43 ` Óscar Fuentes
2021-10-14 6:33 ` Eli Zaretskii
2021-10-14 15:59 ` H. Dieter Wilhelm
2021-10-14 16:41 ` Eli Zaretskii
2021-10-15 9:26 ` H. Dieter Wilhelm
2021-10-15 10:58 ` Eli Zaretskii
2021-10-16 9:57 ` H. Dieter Wilhelm
2021-10-18 20:13 ` H. Dieter Wilhelm
2021-10-18 20:34 ` Óscar Fuentes [this message]
2021-10-19 7:00 ` H. Dieter Wilhelm
2021-10-19 19:43 ` H. Dieter Wilhelm
2021-10-20 11:49 ` Eli Zaretskii
2021-10-20 19:15 ` H. Dieter Wilhelm
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=87y26qkr6q.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--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).