From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems. Date: Wed, 08 Nov 2017 20:13:24 +0200 Message-ID: <83y3ngr64b.fsf@gnu.org> References: <84o9pyim1a.fsf@AigleRoyal> <847evr1r3j.fsf@gmail.com> <87y3nh4hsa.fsf@users.sourceforge.net> <831sl8sqmc.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1510164911 4837 195.159.176.226 (8 Nov 2017 18:15:11 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 8 Nov 2017 18:15:11 +0000 (UTC) Cc: fabrice.popineau@gmail.com, f.j.wright@live.co.uk, vincent.belaiche@gmail.com, 28601@debbugs.gnu.org, stephen_leake@stephe-leake.org, phillip.lord@russet.org.uk To: Noam Postavsky Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Nov 08 19:15:07 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 1eCUsT-0000rV-9Z for geb-bug-gnu-emacs@m.gmane.org; Wed, 08 Nov 2017 19:15:05 +0100 Original-Received: from localhost ([::1]:33344 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eCUsX-0005MY-Fo for geb-bug-gnu-emacs@m.gmane.org; Wed, 08 Nov 2017 13:15:09 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55562) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eCUsR-0005MT-Ox for bug-gnu-emacs@gnu.org; Wed, 08 Nov 2017 13:15:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eCUsQ-0006C9-QV for bug-gnu-emacs@gnu.org; Wed, 08 Nov 2017 13:15:03 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:50171) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eCUsQ-0006C3-M4 for bug-gnu-emacs@gnu.org; Wed, 08 Nov 2017 13:15:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eCUsQ-0007vm-Gm for bug-gnu-emacs@gnu.org; Wed, 08 Nov 2017 13:15:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 08 Nov 2017 18:15:02 +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.151016490030461 (code B ref 28601); Wed, 08 Nov 2017 18:15:02 +0000 Original-Received: (at 28601) by debbugs.gnu.org; 8 Nov 2017 18:15:00 +0000 Original-Received: from localhost ([127.0.0.1]:58852 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eCUsO-0007vF-9i for submit@debbugs.gnu.org; Wed, 08 Nov 2017 13:15:00 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:36296) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eCUsN-0007v1-AS for 28601@debbugs.gnu.org; Wed, 08 Nov 2017 13:14:59 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eCUsH-00069K-4A for 28601@debbugs.gnu.org; Wed, 08 Nov 2017 13:14:54 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:49734) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eCUqt-0005hU-EL; Wed, 08 Nov 2017 13:13:27 -0500 Original-Received: from [176.228.60.248] (port=2159 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eCUqr-0007n4-Bc; Wed, 08 Nov 2017 13:13:26 -0500 In-reply-to: (message from Noam Postavsky on Wed, 8 Nov 2017 12:42:29 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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:139616 Archived-At: > From: Noam Postavsky > Date: Wed, 8 Nov 2017 12:42:29 -0500 > Cc: Vincent Belaïche , > Glenn Morris , 28601@debbugs.gnu.org, Francis Wright , > Stephen Leake , Phillip Lord , > Fabrice Popineau > > > (Btw, on my system, "type gcc" from Bash says "/d/usr/bin/gcc", and > > there's nothing wrong with my installation. So this advice could be > > okay for the newbies, but if the value is different, it doesn't yet > > mean the installation is wrong. I'm just saying.) > > But you have MSYS (1), right? Yes, but it doesn't matter. MSYS2 didn't (and couldn't) change the basic facts that I'll try explaining below. > The issue here, is that with MSYS2 there are 3 possible gcc's that > can be installed. The mingw64 one should be active. If the user > launched C:\msys64\msys2.exe instead of C:\msys64\mingw64.exe, they > would get "/usr/bin/gcc", which is not the right gcc (it would > result in the "Emacs does not support 'x86_64-pc-msys' systems" > error mentioned in the bug title). All of this is only true if your installation is the "canonical" one, in which case MinGW and MSYS are installed under the same common parent, but in sibling subdirectories. But that's not the only valid installation. The only important thing is that the MinGW programs, including GCC, are on the Windows PATH, because then they can be invoked both from MSYS Bash and from anywhere else on the system (including from Emacs which was run via anything except Bash). There are no other requirements for a healthy MinGW installation. If someone installed MSYS gcc (why did they? it's not needed, and they are shooting themselves in the foot), they just need to make sure it's mentioned on PATH after the MinGW one, or even doesn't appear at all on the Windows PATH, only on the MSYS PATH set by .bashrc and friends. IOW, what we are advertising here is only one particular setup, which just happens to be what the MSYS2 crowd decided for you. It is incorrect to say that any other setup is wrong. > >> +** Check your MSYS2 fstab file > > > > I don't understand why this part is necessary. AFAIR, fstab is set up > > by the MSYS installer, and if it doesn't have the correct entries, > > nothing will really work. So I think this problem can only happen if > > someone manually tinkers with their fstab, and if so, they should know > > what they are doing. Asking people to look there runs the risk of > > them deciding that the value is somehow incorrect, and editing it to > > completely ruin their MSYS installation. FWIW, I have _never_ needed > > to look at that file, in all the years I have an actively maintained > > and used MSYS installation. > > > > So I think this is best skipped. > > Maybe we should title the section "If your name is Vincent, Check your > MSYS2 fstab file" ;) Fine with me. Thanks.