From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Building Emacs from a new MinGW environment
Date: Mon, 26 Aug 2013 22:38:23 +0300 [thread overview]
Message-ID: <83sixwfdjk.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0jtH8_22XOr4bCttaKzoBDDf_1hkv2pJkYuK2KbYOJiUg@mail.gmail.com>
> Date: Mon, 26 Aug 2013 20:38:23 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
>
> today, I've noticed that the MinGW developers have recently released a
> new graphical installation & setup tool: mingw-get-setup.exe [1].
>
> I've tried it, and I've easily set up a brand new MinGW (+MSYS)
> development environment.
Don't. The "brand new MinGW" is binary incompatible with the previous
versions (read the small print in the NEWS file). Which means that
all of the DLLs you download from 3rd-party sites, including those
ported by me, and also most of those distributed by MinGW themselves,
are suddenly prone to subtle breakage. In fact, even without any
DLLs, the new startup code pulls in functions like readdir, which are
incompatible with what Emacs defines and uses. Last time I tried to
link Emacs with the new MinGW runtime, wildcard expansion on the
command line stopped working.
(At the time, I tried, but failed miserably, to convince the MinGW
developers that these binary incompatibilities are a bad idea.)
So I advise you to stay with 3.20 for the time being, as I currently
see no way of reconciling these incompatibilities, and don't intend to
invest any effort in that.
next prev parent reply other threads:[~2013-08-26 19:38 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 18:38 Building Emacs from a new MinGW environment Dani Moncayo
2013-08-26 19:38 ` Eli Zaretskii [this message]
2013-08-26 20:08 ` Dani Moncayo
2013-09-13 14:31 ` Dani Moncayo
2013-09-14 9:32 ` Eli Zaretskii
2013-09-14 9:41 ` Dani Moncayo
2013-09-14 10:07 ` Eli Zaretskii
2013-09-14 14:25 ` Dani Moncayo
2013-09-14 14:50 ` Eli Zaretskii
2013-09-14 15:42 ` Dani Moncayo
2013-09-14 16:10 ` Eli Zaretskii
2013-09-14 16:34 ` Dani Moncayo
2013-09-14 17:18 ` Eli Zaretskii
2013-09-14 19:57 ` Dani Moncayo
2013-09-14 20:56 ` Eli Zaretskii
2013-09-14 21:19 ` Dani Moncayo
2013-09-14 22:30 ` Dani Moncayo
2013-09-15 9:35 ` Eli Zaretskii
2013-09-15 9:28 ` Eli Zaretskii
2013-09-16 16:48 ` Dani Moncayo
2013-09-16 17:37 ` Eli Zaretskii
2013-09-16 19:25 ` Dani Moncayo
2013-09-16 19:40 ` Eli Zaretskii
2013-09-16 19:44 ` Dani Moncayo
2013-09-16 20:19 ` Eli Zaretskii
2013-09-17 7:16 ` Eli Zaretskii
2013-09-17 8:17 ` Dani Moncayo
2013-09-17 8:30 ` Eli Zaretskii
2013-09-17 16:09 ` Dani Moncayo
2013-09-17 16:17 ` Glenn Morris
2013-09-17 17:27 ` Eli Zaretskii
2013-09-17 20:29 ` Dani Moncayo
2013-09-18 7:46 ` Eli Zaretskii
2013-09-18 9:32 ` Dani Moncayo
2013-09-18 10:00 ` Eli Zaretskii
2013-09-18 10:38 ` Dani Moncayo
2013-09-18 11:21 ` Eli Zaretskii
2013-09-18 12:39 ` Dani Moncayo
2013-09-18 12:31 ` Dani Moncayo
2013-09-18 13:14 ` Eli Zaretskii
2013-09-18 16:51 ` Dani Moncayo
2013-09-18 19:20 ` Eli Zaretskii
2013-09-19 22:56 ` Dani Moncayo
2013-09-20 8:14 ` Eli Zaretskii
2013-09-20 9:29 ` Andy Moreton
2013-09-20 11:08 ` Dani Moncayo
2013-09-20 11:21 ` Eli Zaretskii
2013-09-20 12:22 ` Dani Moncayo
2013-09-20 12:30 ` Dani Moncayo
2013-09-20 13:16 ` Eli Zaretskii
2013-09-20 13:12 ` Eli Zaretskii
2013-09-20 14:12 ` Eli Zaretskii
2013-09-20 15:05 ` Dani Moncayo
2013-09-18 10:46 ` Andy Moreton
2013-09-18 11:24 ` Eli Zaretskii
2013-09-18 12:44 ` Sean Sieger
2013-09-18 13:16 ` Eli Zaretskii
2013-09-18 13:19 ` Sean Sieger
2013-09-18 14:33 ` Eli Zaretskii
2013-09-18 13:21 ` Andy Moreton
2013-09-18 14:45 ` Eli Zaretskii
2013-09-18 20:51 ` Andy Moreton
2013-09-19 8:45 ` Eli Zaretskii
2013-09-19 8:56 ` Dani Moncayo
2013-09-19 9:38 ` Eli Zaretskii
2013-09-19 10:04 ` Dani Moncayo
2013-09-19 10:11 ` Eli Zaretskii
2013-11-09 14:47 ` Dani Moncayo
2013-11-10 16:32 ` Dani Moncayo
2013-11-12 2:56 ` Glenn Morris
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=83sixwfdjk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmoncayo@gmail.com \
--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 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.