From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: vincent.belaiche@gmail.com (Vincent =?UTF-8?Q?Bela=C3=AFche?=) Newsgroups: gmane.emacs.bugs Subject: bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems. Date: Mon, 16 Oct 2017 19:11:24 +0200 Message-ID: <84376jaugz.fsf@gmail.com> References: <84o9pyim1a.fsf@AigleRoyal> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1508173960 19137 195.159.176.226 (16 Oct 2017 17:12:40 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 16 Oct 2017 17:12:40 +0000 (UTC) Cc: 28601@debbugs.gnu.org, Vincent =?UTF-8?Q?Bela=C3=AFche?= To: Noam Postavsky Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Oct 16 19:12:33 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1e48w2-0001d3-Kl for geb-bug-gnu-emacs@m.gmane.org; Mon, 16 Oct 2017 19:12:14 +0200 Original-Received: from localhost ([::1]:34221 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e48w9-0004PZ-K9 for geb-bug-gnu-emacs@m.gmane.org; Mon, 16 Oct 2017 13:12:21 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48512) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e48vu-0004LQ-NZ for bug-gnu-emacs@gnu.org; Mon, 16 Oct 2017 13:12:12 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e48vq-0008RX-2j for bug-gnu-emacs@gnu.org; Mon, 16 Oct 2017 13:12:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:35453) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e48vp-0008RC-V2 for bug-gnu-emacs@gnu.org; Mon, 16 Oct 2017 13:12:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e48vp-0006TY-N9 for bug-gnu-emacs@gnu.org; Mon, 16 Oct 2017 13:12:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: vincent.belaiche@gmail.com (Vincent =?UTF-8?Q?Bela=C3=AFche?=) Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 16 Oct 2017 17:12:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 28601 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 28601-submit@debbugs.gnu.org id=B28601.150817388424843 (code B ref 28601); Mon, 16 Oct 2017 17:12:01 +0000 Original-Received: (at 28601) by debbugs.gnu.org; 16 Oct 2017 17:11:24 +0000 Original-Received: from localhost ([127.0.0.1]:44134 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e48vD-0006Sb-Tx for submit@debbugs.gnu.org; Mon, 16 Oct 2017 13:11:24 -0400 Original-Received: from mail-wr0-f177.google.com ([209.85.128.177]:46885) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e48vC-0006SP-1r for 28601@debbugs.gnu.org; Mon, 16 Oct 2017 13:11:22 -0400 Original-Received: by mail-wr0-f177.google.com with SMTP id l1so3650910wrc.3 for <28601@debbugs.gnu.org>; Mon, 16 Oct 2017 10:11:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:date:message-id:mime-version :content-transfer-encoding; bh=EevY4RUAL5wqfmDHvoxcBZs1kmA8qInG6/KalolHX+A=; b=I8Q1FELTntL57FF0T9xpWuDxep4GIUbYHiFw19KvFNcCvdstbzOC+qrjR4dVdka8MZ Rc6OLIcIQa6feYAksT36bZ8h1jC1XjHRj5gB3wTZK9KYMpGbxJ4fOmt73nvCzJHY1rSK cbili+hZN7wNUYbRXDRG9X0VNcsY5OF9wiosUxJ+pBcR74Z78wABozx2N7Hvra4kzlFr PpJZgqwGY76u1DBm3BlBv0qQ55MECaIu4KdTFQXXlAZGUWOTYwTI46xtdAG2/ctZJ+ya Rhs9sNdQzzVCQLW8e2a624wes4Rs9yNliSPzYzAF0RDV1CDrY4K23j8d6Ecnl4uYXFql ToNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:date:message-id :mime-version:content-transfer-encoding; bh=EevY4RUAL5wqfmDHvoxcBZs1kmA8qInG6/KalolHX+A=; b=aAcnTIr+4Br1rguk2SSOInseMBwzY0WpiS25QuxAUroft14k2u0rLJ5oK9tmJn8h+7 y6eGBD2S7pxOM1ep3wJPaFhM0jfMrPVjGFzY0J8N55RVB3Xeb0fBC7iaFiYbPNDZF5l1 5V9lUza9FWQLEzPxAWQR/6130LYnK55Rv4mw+n53UlJlpdas9FMsvHmmpSSZhaoxaMwx pD6OtVJYQ6ce+NNScUgsHyD8daXrNarvGxX4e7VHWce1EQKBViHmbqhnB41/tFhkSNsw wb5MNPGhnhScFrXq2NhKNnm3c87mNtIBAdoF9YHs0DemUuiFHqrXkYa+mfdTKRKmiQVa RoLQ== X-Gm-Message-State: AMCzsaX7uZZMCkZrx6j2y7HFTTcOHKIssOjjWNfmd6ASzuxMz0mrpHgS Jf3C/fNp6CCK37zMMO5aNFxLDU+j X-Google-Smtp-Source: ABhQp+RkvuXTEk3PEfwRifCOXO9oyaipMWN+z0okG6QWEKojHm7fwlRM2SgeuyxeTo6b4/cMlWOJDw== X-Received: by 10.223.187.65 with SMTP id x1mr1174766wrg.26.1508173875922; Mon, 16 Oct 2017 10:11:15 -0700 (PDT) Original-Received: from AigleRoyal (ARennes-656-1-275-111.w109-218.abo.wanadoo.fr. [109.218.75.111]) by smtp.gmail.com with ESMTPSA id b15sm6523382wrh.35.2017.10.16.10.11.13 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 16 Oct 2017 10:11:14 -0700 (PDT) In-Reply-To: X-Antivirus: Avast (VPS 171016-2, 16/10/2017), Outbound message X-Antivirus-Status: Clean X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:138542 Archived-At: Dear Noam, Answers embedded below... Le 16/10/2017 =E0 16:23, Noam Postavsky a =E9crit : > On Mon, Oct 16, 2017 at 4:59 AM, Vincent Bela=EFche > wrote: > >> I attached a patch to INSTALL.W64 to collect all the instruction needed >> in my case to install Emacs. > >> +In the sequel we denote by c:\MSYS\INSTALL\DIR\msys64 the >> +directory where MSYS2 is installed, e.g. C:\msys64 by default. > > I think just using the default C:\msys64 might be clearer than using > this kind of meta-syntax. > OK, I will revise that. >> + >> +* Configure your MSWindows PATH variable >> + >> Then you'll need to add the following directories to your Windows PATH >> environment variable: >> >> - c:\msys64\usr\bin;c:\msys64\mingw64\bin >> + c:\MSYS\INSTALL\DIR\msys64\usr\bin;c:\MSYS\INSTALL\DIR\msys64\mingw64= \bin >> + >> +where c:\MSYS\INSTALL\DIR\msys64 depends on your MSYS2 installation, >> +and is c:\msys64 by default. >> >> -you can do this through Control Panel / System and Security / System / >> +You can do this through Control Panel / System and Security / System / >> Advanced system settings / Environment Variables / Edit path. >> >> Adding these directories to your PATH tells Emacs where to find the DLL= s it >> needs to run, and some optional commands like grep and find. These com= mands >> will also be available at the Windows console. >> >> +Concerning the find command see also the last step about configuring >> +your init file to get an MSWindows find port. >> + > > Actually I never changed my Windows PATH. Running Emacs 25 outside of > the MSYS2 environment complains about not finding libwinpthread-1.dll, > but Emacs 26 works fine. Perhaps we can just remove this section > entirely? > I does not work for me if I don't change MSWindows PATH. But the text needs revision anyway because it does not say what has to be ensured. What happens for me is that c:\MSYS\INSTALL\DIR\msys64\mingw64\bin has to be high enough in the path list, otherwise Emacs gets frozen on start. I have not fully identified how high it has to be. It seems that if it is not before c:\Perl64\site\bin then the freeze happens (to be confirmed by more tests). c:\Perl64\site\bin is some ActiveState native perl implementation which contains a gcc.exe executable but no DLL's. >> ** Download and install the necessary packages > >> + for w in msys/msys2-launcher-git \ > > Is there some reason you changed to a for loop? > Yes, I had some packages already installed, and if I just type pacman -S msys/msys2-launcher-git \ msys/m4 \ msys/autoconf \ msys/grep \ msys/findutils \ mingw64/mingw-w64-x86_64-pkg-config \ mingw64/mingw-w64-x86_64-make \ mingw64/mingw-w64-x86_64-toolchain \ mingw64/mingw-w64-x86_64-xpm-nox \ mingw64/mingw-w64-x86_64-libtiff \ mingw64/mingw-w64-x86_64-giflib \ mingw64/mingw-w64-x86_64-libpng \ mingw64/mingw-w64-x86_64-libjpeg-turbo \ mingw64/mingw-w64-x86_64-librsvg \ mingw64/mingw-w64-x86_64-liblcms2 \ mingw64/mingw-w64-x86_64-libxml2 \ mingw64/mingw-w64-x86_64-gnutls \ mingw64/mingw-w64-x86_64-zlib and I type ENTER for defaulting to =AB=A0all=A0=BB then it seems that pacma= n does not really re-install anything. With a look thing are handled one by one more cleanly, and it is easier for the user to discriminate. I must admit that I have not really checked that nothing is re-installed: it is just that after ENTER pacman exits immediatly with saying that it is reinstalled, but I cannot believe that it was done in almost no time. >> +** Check your MSYS2 fstab file > > Do you mean that your fstab file was broken somehow? I never even > looked at mine. MSYS2 was already installed for me some time ago, because I needed a more recent GNU-make to generate some LaTeX package distribution (the MSYS1 GNU-Make is bogous with memort handling). So I had already edited manually the fstab to mount MiKTeX binary directory to /miktex/bin and have this /miktex/bin in my PATH as set by my ~/.bashrc. It seems that having done that prevent MSYS2 pacman to update the fstab when mingw64 stuff is added --- or maybe pacman never tampers with the fstab, and the /mingw64 mount point was added later than the time when I installed MSYS2. > >> +Otherwise, you will need to exit the MINGW64 console and edit your >> +~/.bashrc file, where ~ denote >> +c:\MSYS\INSTALL\DIR\msys64\home\%USERNAME%, to have the correct PATH >> +variable from MSYS/MINGW32/MINGW64 consoles: >> + >> +In this cas, please make sure that ~/.bashrc contains some statement >> +like: > > Do you mean you needed to modify your ~/.bashrc to get the correct > PATH under mingw64.exe? It should already be set correctly by > /etc/profile. > Well, I have tampered with the original msys2_shell.cmd (what pre-existed before the launchers were made available) in order to activate MSWindows native symlinks when I open an MSYS2 console. See https://github.com/msys2/msys2/issues/71 This works fine, but for some reason when I do that (which amounts to launching the MSYS2 console through the COM "Shell.Application" with the "runas" method) then the MSYS2 PATH is the same as my MSWindows PATH (so it does not contain the /usr/bin etc...). So, to work around this, my ~/.bashrc sets the PATH from scratch w/o using the value at bash start-up. This means that whether I use mingw64.exe, mingw32.exe or msys2.exe does not make any difference to me, and only the ~/.bashrc matters. Reading again my modified msys2_shell.cmd script and the profile script, I think that this issue arose from MSYS2_PATH_TYPE not being exported to the process env that contains the lauched console. This is because all the msys2_shell.cmd is under setlocal regime. Anyway, as you see it is better if the user check that the PATH is correctly set in case that, like me the ~/.bashrc makes some tricks. > Perhaps we can put this under a "Troubleshooting" section at the end. Yes, I agree that I was a little naughty, and my troubles were partly caused by too much hacking. Vincent. --- L'absence de virus dans ce courrier =E9lectronique a =E9t=E9 v=E9rifi=E9e p= ar le logiciel antivirus Avast. https://www.avast.com/antivirus