From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Emacs for Windows Date: Sun, 12 Oct 2014 09:11:14 +0300 Message-ID: <83a95195rx.fsf@gnu.org> References: <874mvcc1jh.fsf@gmail.com> <83d2a0bfwu.fsf@gnu.org> <83y4so9jjy.fsf@gnu.org> <87bnpimxal.fsf@wanadoo.es> <83siiu8ux9.fsf@gnu.org> <877g06mw9n.fsf@wanadoo.es> <83oati8uek.fsf@gnu.org> <8738aumvf9.fsf@wanadoo.es> <83mw928sd0.fsf@gnu.org> <87ppdyl7iw.fsf@wanadoo.es> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Trace: ger.gmane.org 1413094312 11710 80.91.229.3 (12 Oct 2014 06:11:52 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 12 Oct 2014 06:11:52 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Oct 12 08:11:46 2014 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XdCNd-0005wO-Qg for geh-help-gnu-emacs@m.gmane.org; Sun, 12 Oct 2014 08:11:45 +0200 Original-Received: from localhost ([::1]:56229 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdCNd-00079H-CN for geh-help-gnu-emacs@m.gmane.org; Sun, 12 Oct 2014 02:11:45 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59173) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdCNO-00078A-1D for help-gnu-emacs@gnu.org; Sun, 12 Oct 2014 02:11:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XdCNI-0008U2-Md for help-gnu-emacs@gnu.org; Sun, 12 Oct 2014 02:11:29 -0400 Original-Received: from mtaout28.012.net.il ([80.179.55.184]:46537) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XdCNI-0008Tw-9f for help-gnu-emacs@gnu.org; Sun, 12 Oct 2014 02:11:24 -0400 Original-Received: from conversion-daemon.mtaout28.012.net.il by mtaout28.012.net.il (HyperSendmail v2007.08) id <0NDB00I00IFIME00@mtaout28.012.net.il> for help-gnu-emacs@gnu.org; Sun, 12 Oct 2014 09:09:47 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout28.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NDB00AGUIGBVN70@mtaout28.012.net.il> for help-gnu-emacs@gnu.org; Sun, 12 Oct 2014 09:09:47 +0300 (IDT) In-reply-to: <87ppdyl7iw.fsf@wanadoo.es> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.184 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:100443 Archived-At: > From: =D3scar Fuentes > Date: Sat, 11 Oct 2014 21:40:23 +0200 >=20 > > Btw, I reviewed a few patches they have in github for a couple of > > packages with which I'm familiar, and either the patches availabl= e > > through github are not all the story (e.g., perhaps they use some > > additional non-default replacements for standard library function= s), > > or their ports are crippled. Examples include Guile (which needs= to > > be heavily patched to work on Windows) and Hunspell (likewise, an= d one > > of the bugs affects Unix as well). >=20 > Guile is not available as a native package. Then what is https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-guile ? > It depends on the MSYS2 Posix layer. Sorry, I don't understand what that means. Are you saying it's an MSYS2 build, rather than a native MinGW build? If so, why is it in the MinGW tree? > The PKGBUILD and patches are here: >=20 > https://github.com/Alexpux/MSYS2-packages/tree/master/guile This is for MSYS2 Guile. I'm talking about this: https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-guile which has its own PKGBUILD and a patch. > Hunspell es available as a native package: >=20 > $ pacman -Ss hunspe > mingw32/mingw-w64-i686-hunspell 1.3.3-2 > Spell checker and morphological analyzer library and program (m= ingw-w64) > mingw64/mingw-w64-x86_64-hunspell 1.3.3-2 > Spell checker and morphological analyzer library and program (m= ingw-w64) >=20 > but there are some reports about crashes on the bug tracker. Maybe = they > are just discovering the issues you mention. The main problem with the upstream sources, which affects Unix as well, is that Hunspell reports offsets in bytes, not in characters, s= o the Emacs ispell.el interface barfs unless you use a single-byte encoding (whereas the default is to use UTF-8 with Aspell and Hunspell). So this means this port is not useful for Emacs users. > > In addition, at least one package -- Bison 3.0.2 -- has no patche= s at > > all, and no source distro under "Sources", so either it is buggy,= or > > the patches used to build the binaries were not posted. >=20 > bison is available as a MSYS2 package and as a MinGW-w64 package (t= he > "native" counterpart.) For the later, the recipe and patches are he= re: >=20 > https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-bis= on In a hidden place, I see. Anyway, this still leaves us with 4 bugs out of what I discovered just by running the Bison test suite. So again, it doesn't sound like they are running the test suite, or care about the failures it shows, because the bugs that are left cause several dozen of tests fail. > m4 is available as MSYS2 and MinGW-w64 packages: >=20 > $ pacman -Ss m4 > mingw32/mingw-w64-i686-m4 1.4.17-1 > The GNU macro processor (mingw-w64) > mingw64/mingw-w64-x86_64-m4 1.4.17-1 > The GNU macro processor (mingw-w64) > msys/m4 1.4.17-2 (base-devel) [instalado] > The GNU macro processor Somehow missed that, sorry. > Gawk as a MSYS2 package: Since Gawk builds with MinGW out of the box, even without the need to run the configure script, not having a MinGW64 port for it is strange= , to say the least. > Same for flex. Without Flex, you don't have a complete development environment, so again, not offering a MinGW Flex sounds like an omission that should be fixed. > Please note that the project is a just months old and there is no > central authority for ensuring that the submitted build recipes are > sound. If it builds, it is accepted and then they wait for bug repo= rts. > If the package is too broken, it is retracted until someone fixes i= t. My point is that the amount of hype this project generates among its fans is not entirely justified by the evident omissions and (IMO) insufficient QA.