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 18:05:15 +0200 Message-ID: <831sl8sqmc.fsf@gnu.org> References: <84o9pyim1a.fsf@AigleRoyal> <847evr1r3j.fsf@gmail.com> <87y3nh4hsa.fsf@users.sourceforge.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1510157237 2850 195.159.176.226 (8 Nov 2017 16:07:17 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 8 Nov 2017 16:07:17 +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 17:07:11 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 1eCSsh-0000Qy-DE for geb-bug-gnu-emacs@m.gmane.org; Wed, 08 Nov 2017 17:07:11 +0100 Original-Received: from localhost ([::1]:60613 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eCSsn-0003tj-6G for geb-bug-gnu-emacs@m.gmane.org; Wed, 08 Nov 2017 11:07:17 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42890) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eCSsd-0003t9-R0 for bug-gnu-emacs@gnu.org; Wed, 08 Nov 2017 11:07:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eCSsY-0002Ln-3c for bug-gnu-emacs@gnu.org; Wed, 08 Nov 2017 11:07:07 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:50073) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eCSsY-0002Ld-08 for bug-gnu-emacs@gnu.org; Wed, 08 Nov 2017 11:07:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eCSsX-0004gE-QV for bug-gnu-emacs@gnu.org; Wed, 08 Nov 2017 11:07:01 -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 16:07: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.151015720617963 (code B ref 28601); Wed, 08 Nov 2017 16:07:01 +0000 Original-Received: (at 28601) by debbugs.gnu.org; 8 Nov 2017 16:06:46 +0000 Original-Received: from localhost ([127.0.0.1]:58754 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eCSsI-0004fe-7b for submit@debbugs.gnu.org; Wed, 08 Nov 2017 11:06:46 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:51747) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eCSsH-0004fS-4A for 28601@debbugs.gnu.org; Wed, 08 Nov 2017 11:06:45 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eCSsA-00022c-Pf for 28601@debbugs.gnu.org; Wed, 08 Nov 2017 11:06:39 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:47409) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eCSqh-0001AP-0u; Wed, 08 Nov 2017 11:05:07 -0500 Original-Received: from [176.228.60.248] (port=2037 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eCSqg-0000uI-41; Wed, 08 Nov 2017 11:05:06 -0500 In-reply-to: <87y3nh4hsa.fsf@users.sourceforge.net> (message from Noam Postavsky on Tue, 07 Nov 2017 21:37:41 -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:139611 Archived-At: > From: Noam Postavsky > Cc: Glenn Morris , Eli Zaretskii , 28601@debbugs.gnu.org, Francis Wright , Stephen Leake , Phillip Lord , Fabrice Popineau > Date: Tue, 07 Nov 2017 21:37:41 -0500 > > Trying to consolidate recent bug-gnus-emacs and emacs-devel discussion > about this. Thanks. > -Note also that we need to disable Imagemagick because Emacs does not yet > -support it on Windows. > +Note also that we need to disable Imagemagick and DBUS because Emacs > +does not yet support them on Windows. I think the correct spelling is D-Bus, no? > +** Check your $PATH > + > +When building Emacs, you should have /mingw64/bin in $PATH, such that running > + > + which gcc > + > +gives '/mingw64/bin/gcc'. > + > +** Check your $PKG_CONFIG_PATH > + > +It should start with '/mingw64/lib/pkgconfig'. You are talking to Windows users here, they might not be familiar with the Unix shell's $FOO syntax. So I suggest to be more explicit here, something like ** Check your PATH environment variable Also, there are native Windows ports of 'which', so I suggest to say explicitly that "which gcc" should be invoked from the MSYS Bash command line (and if so, why not use "type gcc" instead?). Otherwise, the report by 'which' might be in a very different form, because /mingw64 is not a real Windows file name. (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.) > +** 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. Thanks again for working on this, and thanks to everyone else who contributed to this discussion.