From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: 64-bit build on Windows Date: Fri, 20 Jan 2017 02:40:32 +0100 Message-ID: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=f403045d5d72b6770505467cbe4b X-Trace: blaine.gmane.org 1484876499 32443 195.159.176.226 (20 Jan 2017 01:41:39 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 20 Jan 2017 01:41:39 +0000 (UTC) To: Emacs developers Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 20 02:41:34 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cUOCh-0006g7-Dn for ged-emacs-devel@m.gmane.org; Fri, 20 Jan 2017 02:41:23 +0100 Original-Received: from localhost ([::1]:51900 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUOCi-0006SV-DR for ged-emacs-devel@m.gmane.org; Thu, 19 Jan 2017 20:41:24 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46695) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cUOCb-0006SL-Gx for emacs-devel@gnu.org; Thu, 19 Jan 2017 20:41:18 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cUOCa-00025P-CS for emacs-devel@gnu.org; Thu, 19 Jan 2017 20:41:17 -0500 Original-Received: from mail-wm0-x235.google.com ([2a00:1450:400c:c09::235]:36427) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cUOCa-00023f-4N for emacs-devel@gnu.org; Thu, 19 Jan 2017 20:41:16 -0500 Original-Received: by mail-wm0-x235.google.com with SMTP id c85so18222185wmi.1 for ; Thu, 19 Jan 2017 17:41:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=E/1p7yas6urL2l4d1dy3fvwr+t3kur7B6X71WCXyBUI=; b=HZJLOe1wCMTbooeb4lbmwNjvyNNoolyzEo6J0tB4BBnWZCCBsU6QmfT/zKjN1eEzn+ 3DYpSTdhfPpCC3yIBz9mfG0PqZBA3x+F59PASn6e0eVrBoCNW8CYesr5xtR9p9v+sSHP 8E7MwRe46y1DP01DMsXgv5obkU4TgvF3+lsFpgVOnz2fP8HWqpVBX1MITB1AXmXpFtzF rDO132vELYQTB6EX9GoThdEQCu0L4YNZx9bDDU7/j8sTOrNVVhKCDRfFw0GXegknGSQk PIrsQ85NLaWJ1D/PsSEQXIgOBCUGocgqNTZktqsKApsa7qetdFg1iJ3Ckrzard7JHTkl 2Fdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=E/1p7yas6urL2l4d1dy3fvwr+t3kur7B6X71WCXyBUI=; b=dYyZJbiTj8Zuq23LMvJDSxXlX2Ni0CHirtC72pl6jET34Ubs6qJvB16Ch58m++NiFy hxNMhH5F/TGZTJXVQbeuuWqBS0St1XtHOYlVg+IQnKLK2hlUaFXeHxyGLkhR1mwaKSmB PPqNsu+6+/lZreCuxHvXbZ5fnNwJp+W0x6lGJzODiXgTFfjX1qxPvKEUmYBjtrIx1g7H ApHsHy5c2VzUajC873OInac4JQMgNJwrtCfao3p2xkqF7VVe0C9Ty1L/0mWnwUKtZzfJ OR1pn5cO+ofqUX/XViueXsFuWVAEUPW43yQCb/dgDB0BNbFvPB5YpIv7lR3g5I2PVVMB aoJw== X-Gm-Message-State: AIkVDXK0cPHg+9s+NQt+Bs/OkldH3L5XZuelveHaP2GG6Mk4SMU9d+B9uSyH7NteertN/JL07BkWIey18skGAg== X-Received: by 10.223.153.15 with SMTP id x15mr9404418wrb.179.1484876473070; Thu, 19 Jan 2017 17:41:13 -0800 (PST) Original-Received: by 10.195.24.3 with HTTP; Thu, 19 Jan 2017 17:40:32 -0800 (PST) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:400c:c09::235 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:211417 Archived-At: --f403045d5d72b6770505467cbe4b Content-Type: text/plain; charset=UTF-8 Hi. I've been able to build 64-bit Emacs on Windows with MSYS2. Generally, things went smoothly, except for a couple of small problems. This fragment in nt/INSTALL.64: Note also that we need to disable Imagemagick because Emacs does not yet support it on Windows. PKG_CONFIG_PATH=/mingw64/lib/pkgconfig \ ./configure --prefix=/c/emacs/emacs-25 --without-imagemagick is entirely correct, but confusing if you happen to read it too quickly or carelessly (as I did). The note talks about Imagemagick, but the sample command also includes the setting of PKG_CONFIG_PATH (the only time that pkg-config is mentioned in the file). So my brain dismissed the PKG_CONFIG_PATH line, and went straight for the "./configure [...] --without-imagemagick" part. That didn't end too well. I also used msys2_shell.cmd (though nt/INSTALL.W64 clearly says not to) and got into trouble with the guessed build machine. To be fair, I was misled because nt/INSTALL.64 talks about mingw64_shell.bat, and that file doesn't exist anymore, at least on the default MSYS2 setup you get by following our suggested step-by-step guide. There are new executables mingw32.exe and mingw64.exe, and using the latter I finished the build without further trouble. But surely nt/INSTALL.64 should be fixed to refer to the new launchers, or perhaps include a pointer to https://sourceforge.net/p/msys2/wiki/Launchers/. Juanma --f403045d5d72b6770505467cbe4b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi.

I've been able to build 64-bit Emacs on Win= dows with MSYS2. Generally, things went smoothly, except for a couple of sm= all problems.


This fragment in nt/INSTALL.64:

=C2=A0 Note also that we need to disable Imagemag= ick because Emacs does not yet
=C2=A0 support it on Windows.

=C2= =A0 =C2=A0 PKG_CONFIG_PATH=3D/mingw64/lib/pkgconfig \
=C2=A0 =C2=A0 ./co= nfigure --prefix=3D/c/emacs/emacs-25 --without-imagemagick

is= entirely correct, but confusing if you happen to read it too quickly or ca= relessly (as I did). The note talks about Imagemagick, but the sample comma= nd also includes the setting of PKG_CONFIG_PATH (the only time that pkg-con= fig is mentioned in the file). So my brain dismissed the PKG_CONFIG_PATH li= ne, and went straight for the "./configure [...] --without-imagemagick= " part. That didn't end too well.


I also used msys2_she= ll.cmd (though nt/INSTALL.W64 clearly says not to) and got into trouble wit= h the guessed build machine. To be fair, I was misled because nt/INSTALL.64= talks about mingw64_shell.bat, and that file doesn't exist anymore, at= least on the default MSYS2 setup you get by following our suggested step-b= y-step guide. There are new executables mingw32.exe and mingw64.exe, and us= ing the latter I finished the build without further trouble. But surely nt/= INSTALL.64 should be fixed to refer to the new launchers, or perhaps includ= e a pointer to=C2=A0https://sourceforge.net/p/msys2/wiki/Launchers/.

=C2=A0 =C2=A0 Juanma
--f403045d5d72b6770505467cbe4b--