From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org
Subject: Latest MinGW runtime and Windows 9X
Date: Fri, 06 Dec 2013 09:55:07 +0200 [thread overview]
Message-ID: <831u1q2z38.fsf@gnu.org> (raw)
People who produce Windows binaries for Emacs should read the
discussion that started here (and is still on-going):
https://sourceforge.net/mailarchive/forum.php?thread_name=E8DFAC56-DC81-45DB-B402-0EF5826CBB21%40eznet.net&forum_name=mingw-users
In particular, this message by one of the core MinGW developers:
https://sourceforge.net/mailarchive/forum.php?thread_name=52A0FD08.8090107%40users.sourceforge.net&forum_name=mingw-users
It sounds like at least the official Emacs releases uploaded to
ftp.gnu.org should be built using MinGW runtime 3.x, not the recent
4.x, until and unless these issues are resolved in a way that support
for Windows 9X is not dropped by MinGW, or until Emacs development
decides to end such support.
reply other threads:[~2013-12-06 7:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=831u1q2z38.fsf@gnu.org \
--to=eliz@gnu.org \
--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).