bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

classic Classic list List threaded Threaded
26 messages Options
12
Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Vincent Belaïche-2

I am trying to re-compile Emacs on MSW10 + MSYS2. This used to be
working, but now I get the following error:

--8<----8<----8<----8<----8<-- begin -->8---->8---->8---->8---->8----
checking build system type... x86_64-pc-msys
checking host system type... x86_64-pc-msys
configure: error: Emacs does not support 'x86_64-pc-msys' systems.
If you think it should, please send a report to [hidden email].
Check 'etc/MACHINES' for recognized configuration names.
--8<----8<----8<----8<----8<--  end  -->8---->8---->8---->8---->8----


In GNU Emacs 26.0.50 (build 1, i686-pc-mingw32)
 of 2017-07-02 built on AIGLEROYAL
Repository revision: 3bab927884c4b795f8545b632328b5d3b632eed3
Windowing system distributor 'Microsoft Corp.', version 10.0.14393
Recent messages:
No match
bash refresh default directory ...
sending >pwd -W

coucou!=>C:/Programmes/installation
]0;/c/Programmes/installation
[32mVincent@AigleRoyal [35m[0m [33m/c/Programmes/installation[0m
$ <=
bash refresh default directory ... done
c:/Programmes/installation/emacs-install

Configured using:
 'configure --prefix=c:/Nos_Programmes/GNU/Emacs --without-jpeg
 --without-tiff --without-gif --without-png 'CFLAGS= -Og -g3 -L
 C:/Programmes/installation/emacs-install/libXpm-3.5.8/src' 'CPPFLAGS=
 -DFOR_MSW=1 -I
 C:/Programmes/installation/emacs-install/libXpm-3.5.8/include -I
 C:/Programmes/installation/emacs-install/libXpm-3.5.8/src -L
 C:/Programmes/installation/emacs-install/libXpm-3.5.8/src'
 PKG_CONFIG=/mingw/bin/pkg-config.exe PKG_CONFIG_PATH=/mingw/bin'

Configured features:
XPM SOUND NOTIFY ACL GNUTLS TOOLKIT_SCROLL_BARS

Important settings:
  value of $LANG: FRA
  locale-coding-system: cp1252

Major mode: Shell

Minor modes in effect:
  compilation-in-progress: (compilation compilation compilation)
  semantic-minor-modes-format: ((:eval (if (or semantic-highlight-edits-mode semantic-show-unmatched-syntax-mode jdee-bug-minor-mode jdee-jdb-minor-mode)  S)))
  global-semanticdb-minor-mode: t
  global-semantic-idle-scheduler-mode: t
  semantic-mode: t
  diff-auto-refine-mode: t
  shell-dirtrack-mode: t
  TeX-PDF-mode: t
  recentf-mode: t
  tooltip-mode: t
  global-eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Load-path shadows:
c:/Programmes/installation/jdee/jdee hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee
c:/Programmes/installation/jdee/jdee-xref hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-xref
c:/Programmes/installation/jdee/jdee-wiz hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-wiz
c:/Programmes/installation/jdee/jdee-widgets hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-widgets
c:/Programmes/installation/jdee/jdee-which-method hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-which-method
c:/Programmes/installation/jdee/jdee-util hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-util
c:/Programmes/installation/jdee/jdee-test hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-test
c:/Programmes/installation/jdee/jdee-stat hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-stat
c:/Programmes/installation/jdee/jdee-stacktrace hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-stacktrace
c:/Programmes/installation/jdee/jdee-run hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-run
c:/Programmes/installation/jdee/jdee-refactor hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-refactor
c:/Programmes/installation/jdee/jdee-project hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-project
c:/Programmes/installation/jdee/jdee-project-file hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-project-file
c:/Programmes/installation/jdee/jdee-plugins hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-plugins
c:/Programmes/installation/jdee/jdee-parse hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-parse
c:/Programmes/installation/jdee/jdee-parse-expr hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-parse-expr
c:/Programmes/installation/jdee/jdee-package hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-package
c:/Programmes/installation/jdee/jdee-open-source hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-open-source
c:/Programmes/installation/jdee/jdee-maven hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-maven
c:/Programmes/installation/jdee/jdee-make hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-make
c:/Programmes/installation/jdee/jdee-log hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-log
c:/Programmes/installation/jdee/jdee-keys hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-keys
c:/Programmes/installation/jdee/jdee-junit hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-junit
c:/Programmes/installation/jdee/jdee-juci hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-juci
c:/Programmes/installation/jdee/jdee-jdk-manager hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-jdk-manager
c:/Programmes/installation/jdee/jdee-jdb hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-jdb
c:/Programmes/installation/jdee/jdee-javadoc hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-javadoc
c:/Programmes/installation/jdee/jdee-javadoc-gen hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-javadoc-gen
c:/Programmes/installation/jdee/jdee-java-properties hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-java-properties
c:/Programmes/installation/jdee/jdee-java-grammar hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-java-grammar
c:/Programmes/installation/jdee/jdee-issues hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-issues
c:/Programmes/installation/jdee/jdee-import hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-import
c:/Programmes/installation/jdee/jdee-imenu hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-imenu
c:/Programmes/installation/jdee/jdee-help hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-help
c:/Programmes/installation/jdee/jdee-gen hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-gen
c:/Programmes/installation/jdee/jdee-font-lock hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-font-lock
c:/Programmes/installation/jdee/jdee-flycheck hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-flycheck
c:/Programmes/installation/jdee/jdee-find hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-find
c:/Programmes/installation/jdee/jdee-files hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-files
c:/Programmes/installation/jdee/jdee-ejb hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-ejb
c:/Programmes/installation/jdee/jdee-ecj-flymake hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-ecj-flymake
c:/Programmes/installation/jdee/jdee-deps hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-deps
c:/Programmes/installation/jdee/jdee-dbs hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-dbs
c:/Programmes/installation/jdee/jdee-dbo hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-dbo
c:/Programmes/installation/jdee/jdee-db hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-db
c:/Programmes/installation/jdee/jdee-cygwin hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-cygwin
c:/Programmes/installation/jdee/jdee-custom hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-custom
c:/Programmes/installation/jdee/jdee-complete hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-complete
c:/Programmes/installation/jdee/jdee-compile hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-compile
c:/Programmes/installation/jdee/jdee-classpath hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-classpath
c:/Programmes/installation/jdee/jdee-class hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-class
c:/Programmes/installation/jdee/jdee-checkstyle hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-checkstyle
c:/Programmes/installation/jdee/jdee-bytecode hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-bytecode
c:/Programmes/installation/jdee/jdee-bug hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-bug
c:/Programmes/installation/jdee/jdee-bsh hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-bsh
c:/Programmes/installation/jdee/jdee-bookmark hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-bookmark
c:/Programmes/installation/jdee/jdee-backend hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-backend
c:/Programmes/installation/jdee/jdee-archive hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-archive
c:/Programmes/installation/jdee/jdee-ant hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-ant
c:/Programmes/installation/jdee/jdee-annotations hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-annotations
c:/Programmes/installation/jdee/jdee-activator hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-activator
c:/Programmes/installation/jdee/jdee-abbrev hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jdee-abbrev
c:/Programmes/installation/jdee/jcomplete hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/jcomplete
c:/Programmes/installation/jdee/efc hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/efc
c:/Programmes/installation/jdee/beanshell hides c:/Users/Vincent/AppData/Roaming/.emacs.d/elpa/jdee-2.4.2/beanshell
c:/Programmes/installation/cedet-install/cedet-git/lisp/speedbar/loaddefs hides c:/Nos_Programmes/GNU/Emacs_build20170702/share/emacs/26.0.50/lisp/loaddefs
c:/Programmes/installation/cedet-install/cedet-git/lisp/speedbar/loaddefs hides c:/Programmes/installation/cedet-install/cedet-git/lisp/cedet/loaddefs

Features:
(shadow emacsbug goto-addr view epa-dired jdee-ant jdee-ejb jdee-make
semantic/edit semantic/tag-file jdee-flycheck semantic/bovine/c hideif
semantic/bovine/c-by semantic/lex-spp semantic/bovine/gcc
semantic/analyze/refs semantic/bovine/make semantic/decorate/include
semantic/decorate/mode semantic/analyze semantic/scope
semantic/analyze/fcn semantic/bovine/make-by semantic/texi
semantic/bovine/el semantic/db-el semantic/bovine semantic/db-mode
semantic/wisent/java-tags semantic/wisent/java-tags-wy semantic/wisent
semantic/wisent/wisent jdee-plugins ffap jdee-javadoc-gen jdee jdee-wiz
jdee-test jdee-archive jdee-stacktrace jdee-refactor jdee-keys jdee-jdb
jdee-java-grammar jdee-which-method jdee-font-lock jdee-issues jdee-help
jdee-gen tempo jdee-find jdee-deps jdee-cygwin jdee-class jdee-bug
jdee-annotations jdee-abbrev jdee-activator flymake jdee-bytecode
jdee-compile jdee-dbs jdee-run jdee-dbo jdee-widgets jdee-db memoize
jdee-jdk-manager jdee-project-file jdee-maven jdee-open-source
semantic/senator semantic/decorate pulse jdee-import jdee-complete
semantic/idle working fame jdee-parse jdee-imenu semantic/imenu
semantic/sb semantic/sort semantic/db-file semantic/adebug
eieio-datadebug data-debug cedet-files semantic/java semantic/dep
semantic/format semantic/tag-ls semantic/doc semantic/ctxt
semantic/util-modes semantic/util semantic/db-find semantic/db-ref
semantic/db semantic/find eieio-base semantic semantic/tag semantic/lex
semantic/fw mode-local cedet avl-tree etags xref project jdee-log
jdee-custom jdee-backend jdee-bsh jdee-util arc-mode archive-mode efc
jdee-parse-expr beanshell jdee-classpath jdee-files warnings
eieio-compat ert flycheck dash let-alist tar-mode epl autoload pcase
lisp-mnt mm-archive url-http url-gw url-cache url-auth markdown-mode
calc-vec calc-forms tex-info texinfo conf-mode log-view lpr reftex-cite
ibuf-ext ibuffer ibuffer-loaddefs loadhist pp calc-stuff calc-lang
calccomp calc-units calc-aent iso-transl org-table novice cc-langs
tabify bbdb-tex plain-tex ruler-mode hexl cus-edit multi-prompt info rx
cl-print debug eieio-opt speedbar sb-image ezimage dframe help-fns
radix-tree calc-undo pcmpl-gnu mhtml-mode css-mode color eww mm-url
url-queue url url-proxy url-privacy url-expand url-methods url-history
url-cookie url-domsuf url-util shr svg xml browse-url js json imenu
sgml-mode dom flyspell ispell calc-bin cal-china lunar solar cal-dst
cal-bahai cal-islam cal-hebrew cal-julian holidays hol-loaddefs cal-iso
cal-move bug-reference gnus-async gnus-ml cursor-sensor nndraft nnmh
nnfolder cl-extra bbdb-gnus bbdb-mua gnus-agent gnus-srvr gnus-score
score-mode nnvirtual gnus-msg gnus-art mm-uu mml2015 mm-view mml-smime
smime dig nntp gnus-cache gnus-sum gnus-group gnus-undo gnus-start
gnus-cloud nnimap nnmail mail-source utf7 netrc nnoo parse-time
gnus-spec gnus-int gnus-range gnus-win gnus nnheader reftex-auc
find-dired grep cus-start cus-load quail help-mode calc-yank calc-mode
calc-alg calc-menu diary-lib diary-loaddefs reftex-parse texmathp
ediff-vers cc-mode cc-fonts cc-guess cc-menus cc-cmds cc-styles cc-align
cc-engine cc-vars cc-defs perl-mode make-mode org-element org-rmail
org-mhe org-irc org-info org-gnus org-docview doc-view image-mode
org-bibtex bibtex org-bbdb org-w3m org org-macro org-footnote
org-pcomplete org-list org-faces org-entities org-version ob-emacs-lisp
ob ob-tangle ob-ref ob-lob ob-table ob-exp org-src ob-keys ob-comint
ob-core ob-eval org-compat org-macs org-loaddefs find-func cal-tex
cal-menu calendar cal-loaddefs network-stream nsm starttls tls gnutls
mailalias smtpmail qp jka-compr sort mailcap bbdb-com bbdb-message
sendmail mail-extr whitespace log-edit message subr-x puny format-spec
rfc822 mml mml-sec epa derived epg gnus-util rmail rmail-loaddefs
mm-decode mm-bodies mm-encode mail-parse rfc2231 rfc2047 rfc2045 mm-util
ietf-drums mail-prsvr mailabbrev mail-utils gmm-utils mailheader
pcvs-util thingatpt add-log vc-bzr vc-src vc-sccs vc-svn vc-cvs vc-rcs
vc-dir ewoc vc vc-dispatcher rect dired-aux dired-x dired dired-loaddefs
latexenc ediff-merg ediff-wind ediff-diff ediff-mult ediff-help
ediff-init ediff-util ediff preview prv-emacs reftex-dcr reftex
reftex-loaddefs reftex-vars tex-bar tex-buf toolbar-x font-latex latex
tex-ispell tex-style tex-mode compile hl-line misearch multi-isearch
vc-git diff-mode map noutline outline easy-mmode pcmpl-unix sh-script
smie executable shell pcomplete comint ansi-color ring edmacro kmacro
skeleton calc-misc calc-arith calc-ext calc calc-loaddefs calc-macs
tex-mik tex crm advice preview-latex auto-loads tex-site bbdb bbdb-site
timezone bbdb-loaddefs template w32utils cl recentf tree-widget wid-edit
load-path-to-cedet-svn finder-inf package easymenu epg-config
url-handlers url-parse auth-source cl-seq eieio eieio-core cl-macs
eieio-loaddefs password-cache url-vars seq byte-opt gv bytecomp
byte-compile cconv cl-loaddefs cl-lib time-date mule-util tooltip eldoc
electric uniquify ediff-hook vc-hooks lisp-float-type mwheel dos-w32
ls-lisp disp-table term/w32-win w32-win w32-vars term/common-win
tool-bar dnd fontset image regexp-opt fringe tabulated-list replace
newcomment text-mode elisp-mode lisp-mode prog-mode register page
menu-bar rfn-eshadow isearch timer select scroll-bar mouse jit-lock
font-lock syntax facemenu font-core term/tty-colors frame cl-generic
cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech
european ethiopic indian cyrillic chinese composite charscript charprop
case-table epa-hook jka-cmpr-hook help simple abbrev obarray minibuffer
cl-preloaded nadvice loaddefs button faces cus-face macroexp files
text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget hashtable-print-readable backquote w32notify w32 multi-tty
make-network-process emacs)

Memory information:
((conses 8 2792196 346555)
 (symbols 32 78888 1)
 (miscs 32 10012 2150)
 (strings 16 297025 31457)
 (string-bytes 1 8920819)
 (vectors 8 104212)
 (vector-slots 4 2515724 217380)
 (floats 8 1100 918)
 (intervals 28 301184 1560)
 (buffers 516 252))

---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus




Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Glenn Morris-3
Vincent Belaïche wrote:

> I am trying to re-compile Emacs on MSW10 + MSYS2. This used to be
> working, but now I get the following error:
>
> --8<----8<----8<----8<----8<-- begin -->8---->8---->8---->8---->8----
> checking build system type... x86_64-pc-msys
> checking host system type... x86_64-pc-msys
> configure: error: Emacs does not support 'x86_64-pc-msys' systems.

What version of Emacs did this work in?
AFAICS, configure.ac has never accepted *-msys as a host type.

From https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22240#20 :
   
    configure: error: Emacs does not support 'x86_64-pc-msys' systems.
   
    This turned out to be due to not being in the right environment - I
    added the step to switch to the MinGW-w64 environment and now it works
    without specifying the --host, etc.

From nt/INSTALL.W64:

   First we need to switch to the MinGW-w64 environment. Exit the MSYS2
   BASH console and run mingw64_shell.bat in the C:\msys64 folder...

So try that?



Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Vincent Belaïche-2
Hello Glenn,

There is no such thing as a mingw64_shell.bat script, but there is a
msys2_shell.cmd script, which one can launch with the -mingw64 for
MSYSTEM to be set accordingly to MSYSTEM=MINGW64.

When I do that, then I get the following error :

--8<----8<----8<----8<----8<-- begin -->8---->8---->8---->8---->8----
checking build system type... x86_64-w64-mingw32
checking host system type... x86_64-w64-mingw32
checking the compiler's target... x86_64-pc-msys
configure: error: Emacs does not support 'x86_64-pc-msys' systems.
--8<----8<----8<----8<----8<--  end -->8---->8---->8---->8---->8----

BR,
  V.

Le 27/09/2017 à 20:36, Glenn Morris a écrit :

> Vincent Belaïche wrote:
>
>> I am trying to re-compile Emacs on MSW10 + MSYS2. This used to be
>> working, but now I get the following error:
>>
>> --8<----8<----8<----8<----8<-- begin -->8---->8---->8---->8---->8----
>> checking build system type... x86_64-pc-msys
>> checking host system type... x86_64-pc-msys
>> configure: error: Emacs does not support 'x86_64-pc-msys' systems.
> What version of Emacs did this work in?
> AFAICS, configure.ac has never accepted *-msys as a host type.
>
>  From https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22240#20 :
>      
>      configure: error: Emacs does not support 'x86_64-pc-msys' systems.
>      
>      This turned out to be due to not being in the right environment - I
>      added the step to switch to the MinGW-w64 environment and now it works
>      without specifying the --host, etc.
>
>  From nt/INSTALL.W64:
>
>     First we need to switch to the MinGW-w64 environment. Exit the MSYS2
>     BASH console and run mingw64_shell.bat in the C:\msys64 folder...
>
> So try that?


---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus




Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Vincent Belaïche-2
Answering to myself: there is also a -mingw option with which the script
automatically detects whether mingw64 is there and sets it if so, or
otherwise falls back to mingw32.

   V.


Le 27/09/2017 à 21:07, Vincent Belaïche a écrit :

> Hello Glenn,
>
> There is no such thing as a mingw64_shell.bat script, but there is a
> msys2_shell.cmd script, which one can launch with the -mingw64 for
> MSYSTEM to be set accordingly to MSYSTEM=MINGW64.
>
> When I do that, then I get the following error :
>
> --8<----8<----8<----8<----8<-- begin -->8---->8---->8---->8---->8----
> checking build system type... x86_64-w64-mingw32
> checking host system type... x86_64-w64-mingw32
> checking the compiler's target... x86_64-pc-msys
> configure: error: Emacs does not support 'x86_64-pc-msys' systems.
> --8<----8<----8<----8<----8<--  end -->8---->8---->8---->8---->8----
>
> BR,
>  V.
>
> Le 27/09/2017 à 20:36, Glenn Morris a écrit :
>> Vincent Belaïche wrote:
>>
>>> I am trying to re-compile Emacs on MSW10 + MSYS2. This used to be
>>> working, but now I get the following error:
>>>
>>> --8<----8<----8<----8<----8<-- begin -->8---->8---->8---->8---->8----
>>> checking build system type... x86_64-pc-msys
>>> checking host system type... x86_64-pc-msys
>>> configure: error: Emacs does not support 'x86_64-pc-msys' systems.
>> What version of Emacs did this work in?
>> AFAICS, configure.ac has never accepted *-msys as a host type.
>>
>>  From https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22240#20 :
>>           configure: error: Emacs does not support 'x86_64-pc-msys'
>> systems.
>>           This turned out to be due to not being in the right
>> environment - I
>>      added the step to switch to the MinGW-w64 environment and now it
>> works
>>      without specifying the --host, etc.
>>
>>  From nt/INSTALL.W64:
>>
>>     First we need to switch to the MinGW-w64 environment. Exit the MSYS2
>>     BASH console and run mingw64_shell.bat in the C:\msys64 folder...
>>
>> So try that?
>


---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus




Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Glenn Morris-3
In reply to this post by Vincent Belaïche-2
Vincent Belaïche wrote:

> There is no such thing as a mingw64_shell.bat script, but there is a
> msys2_shell.cmd script, which one can launch with the -mingw64 for
> MSYSTEM to be set accordingly to MSYSTEM=MINGW64.

Sounds like MinGW has changed how things work and the instructions in
nt/INSTALL.W64 need updating.

> checking the compiler's target... x86_64-pc-msys
> configure: error: Emacs does not support 'x86_64-pc-msys' systems.

This is MinGW-specific code added in https://debbugs.gnu.org/19111



Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Andy Moreton-3
In reply to this post by Vincent Belaïche-2
On Wed 27 Sep 2017, Glenn Morris wrote:

> Vincent Belaïche wrote:
>
>> There is no such thing as a mingw64_shell.bat script, but there is a
>> msys2_shell.cmd script, which one can launch with the -mingw64 for
>> MSYSTEM to be set accordingly to MSYSTEM=MINGW64.
>
> Sounds like MinGW has changed how things work and the instructions in
> nt/INSTALL.W64 need updating.
>
>> checking the compiler's target... x86_64-pc-msys
>> configure: error: Emacs does not support 'x86_64-pc-msys' systems.
>
> This is MinGW-specific code added in https://debbugs.gnu.org/19111


Newer MSYS2 installations have mingw32.exe, mingw64.exe and msys2.exe for launching a
shell for each of the build environments, which are more convenient for
creating desktop shortcuts. Either of the first two can be used to build
emacs, if the appropriate toolchain is installed.

    AndyM




Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Eli Zaretskii
> From: Andy Moreton <[hidden email]>
> Date: Thu, 28 Sep 2017 14:10:25 +0100
>
> On Wed 27 Sep 2017, Glenn Morris wrote:
>
> > Vincent Belaïche wrote:
> >
> >> There is no such thing as a mingw64_shell.bat script, but there is a
> >> msys2_shell.cmd script, which one can launch with the -mingw64 for
> >> MSYSTEM to be set accordingly to MSYSTEM=MINGW64.
> >
> > Sounds like MinGW has changed how things work and the instructions in
> > nt/INSTALL.W64 need updating.
> >
> >> checking the compiler's target... x86_64-pc-msys
> >> configure: error: Emacs does not support 'x86_64-pc-msys' systems.
> >
> > This is MinGW-specific code added in https://debbugs.gnu.org/19111
>
>
> Newer MSYS2 installations have mingw32.exe, mingw64.exe and msys2.exe for launching a
> shell for each of the build environments, which are more convenient for
> creating desktop shortcuts. Either of the first two can be used to build
> emacs, if the appropriate toolchain is installed.

Can you or someone else suggest a change for INSTALL.W64, if some
change is needed there?

Thanks.



Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Noam Postavsky-2
On Fri, Sep 29, 2017 at 5:37 AM, Eli Zaretskii <[hidden email]> wrote:

>> > Vincent Belaďche wrote:
>> >
>> >> There is no such thing as a mingw64_shell.bat script, but there is a
>> >> msys2_shell.cmd script, which one can launch with the -mingw64 for
>> >> MSYSTEM to be set accordingly to MSYSTEM=MINGW64.

> Can you or someone else suggest a change for INSTALL.W64, if some
> change is needed there?

The attached should do it.

0001-nt-INSTALL.W64-Use-mingw64.exe-instead-of-mingw64_sh.patch (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Eli Zaretskii
> From: Noam Postavsky <[hidden email]>
> Date: Thu, 12 Oct 2017 19:06:56 -0400
> Cc: Andy Moreton <[hidden email]>, [hidden email],
> Vincent Belaïche <[hidden email]>
>
> -First we need to switch to the MinGW-w64 environment.  Exit the MSYS2 BASH
> -console and run mingw64_shell.bat in the C:\msys64 folder, then cd back to
> +First we need to switch to the MinGW-w64 environment.  Exit the MSYS2
> +BASH console and run mingw64.exe in the C:\msys64 folder (if it's
> +missing, install it with 'pacman -S msys2-launcher'), then cd back to
>  your Emacs source directory, e.g.:

Can we rely on all the users to have the latest MSYS2?  If not,
perhaps after your description we should say something like "If you
don't have mingw64.exe, but do have mingw64_shell.bat, then ..."?

Thanks.



Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Andy Moreton-3
In reply to this post by Vincent Belaïche-2
On Fri 13 Oct 2017, Eli Zaretskii wrote:

>> From: Noam Postavsky <[hidden email]>
>> Date: Thu, 12 Oct 2017 19:06:56 -0400
>> Cc: Andy Moreton <[hidden email]>, [hidden email],
>> Vincent Belaïche <[hidden email]>
>>
>> -First we need to switch to the MinGW-w64 environment.  Exit the MSYS2 BASH
>> -console and run mingw64_shell.bat in the C:\msys64 folder, then cd back to
>> +First we need to switch to the MinGW-w64 environment.  Exit the MSYS2
>> +BASH console and run mingw64.exe in the C:\msys64 folder (if it's
>> +missing, install it with 'pacman -S msys2-launcher'), then cd back to
>>  your Emacs source directory, e.g.:
>
> Can we rely on all the users to have the latest MSYS2?  If not,
> perhaps after your description we should say something like "If you
> don't have mingw64.exe, but do have mingw64_shell.bat, then ..."?

MSYS2 is a rolling-release distribution, so any user who does not have
an up to date installation would be well advised to update to current
package versions before attempting to build emacs.

    AndyM




Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Eli Zaretskii
> From: Andy Moreton <[hidden email]>
> Date: Fri, 13 Oct 2017 11:14:37 +0100
>
> > Can we rely on all the users to have the latest MSYS2?  If not,
> > perhaps after your description we should say something like "If you
> > don't have mingw64.exe, but do have mingw64_shell.bat, then ..."?
>
> MSYS2 is a rolling-release distribution, so any user who does not have
> an up to date installation would be well advised to update to current
> package versions before attempting to build emacs.

I understand, but "advised" doesn't mean "forced", does it?



Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Andy Moreton-3
In reply to this post by Vincent Belaïche-2
On Fri 13 Oct 2017, Eli Zaretskii wrote:

>> From: Andy Moreton <[hidden email]>
>> Date: Fri, 13 Oct 2017 11:14:37 +0100
>>
>> > Can we rely on all the users to have the latest MSYS2?  If not,
>> > perhaps after your description we should say something like "If you
>> > don't have mingw64.exe, but do have mingw64_shell.bat, then ..."?
>>
>> MSYS2 is a rolling-release distribution, so any user who does not have
>> an up to date installation would be well advised to update to current
>> package versions before attempting to build emacs.
>
> I understand, but "advised" doesn't mean "forced", does it?

No, in that things only get updated if you run pacman. However I thnk
the first respone to "I have a problem" will be "update to current
package versions".

    AndyM




Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Vincent Belaïche-2
In reply to this post by Glenn Morris-3
Dear Glenn, Noam, Eli, & al.

I realize that I have not answered to you Glenn. My latest build of
Emacs is:

        GNU Emacs 26.0.50 (build 1, i686-pc-mingw32) of 2017-07-02

It was done with MSYS1. I see that that platform is ...-mingw32 and not
-msys which explains why it worked.

I switched from MSYS1 to MSYS2 at end of July 2017 because I had too
many problems with MSYS1 not being supported any longer (see for
instance http://savannah.gnu.org/bugs/?51527 about MSYS1 GNUMake issue,
I really, really should have done this switch earlier ...).

Now, I did the:

        pacman -S msys2-launcher

as recommended in the INSTALL.W64 patch from Noam, and then I launched
msys64.exe from the MSWindows exporer. But it still does not work, I get
that the compiler target is still x86_64-pc-msys, which is not accepted
by configure.

The reason for this, is that my configure command does not have any
--host option, FYI here it is:

        ./configure --prefix=c:/Nos_Programmes/GNU/Emacs --without-jpeg --without-tiff --without-gif --without-png 'CFLAGS= -Og -g3 -L C:/Programmes/installation/emacs-install/libXpm-3.5.8/src' 'CPPFLAGS= -DFOR_MSW=1 -I C:/Programmes/installation/emacs-install/libXpm-3.5.8/include -I C:/Programmes/installation/emacs-install/libXpm-3.5.8/src -L C:/Programmes/installation/emacs-install/libXpm-3.5.8/src' PKG_CONFIG=/mingw/bin/pkg-config.exe PKG_CONFIG_PATH=/mingw/bin --no-create --no-recursion

so the configure script tries to know the right host by doing gcc -v,
this test is just after this comment in configure:

        # No --host argument was given to 'configure'; therefore $host
        # was set to a default value based on the build platform.  But
        # this default value may be wrong if we are building from a
        # 64-bit MSYS[2] pre-configured to build 32-bit MinGW programs.
        # Therefore, we'll try to get the right host platform from the
        # compiler's target.

When I launch mingw64 and then I do

        { LC_ALL=C gcc -v 2>&1; } | grep Target

I get this :

   Target: x86_64-pc-msys

Hence the error which I reported in the first place :.

        checking the compiler's target... x86_64-pc-msys
        configure: error: Emacs does not support 'x86_64-pc-msys' systems.

So, maybe the INSTALL.W64 should contain some recommendation to use the
--host option in some way to work around this.

Please note that gcc -v makes this output even though my MSYSTEM envvar
expands to MINGW64.

I think that the objective of the gcc -v is to discriminate between 32
and 64 bits, not between MINGW and MSYS. So, it seems that what we have
is an autoconf bug. Am I wrong ?

   Vincent.

Le 27/09/2017 à 23:37, Glenn Morris a écrit :

> Vincent Belaïche wrote:
>
>> There is no such thing as a mingw64_shell.bat script, but there is a
>> msys2_shell.cmd script, which one can launch with the -mingw64 for
>> MSYSTEM to be set accordingly to MSYSTEM=MINGW64.
>
> Sounds like MinGW has changed how things work and the instructions in
> nt/INSTALL.W64 need updating.
>
>> checking the compiler's target... x86_64-pc-msys
>> configure: error: Emacs does not support 'x86_64-pc-msys' systems.
>
> This is MinGW-specific code added in https://debbugs.gnu.org/19111


---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus




Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Noam Postavsky-2
On Fri, Oct 13, 2017 at 10:09 AM, Vincent Belaïche
<[hidden email]> wrote:

> Please note that gcc -v makes this output even though my MSYSTEM envvar
> expands to MINGW64.
>
> I think that the objective of the gcc -v is to discriminate between 32
> and 64 bits, not between MINGW and MSYS. So, it seems that what we have
> is an autoconf bug. Am I wrong ?

I think it means you didn't install the mingw-w64-x86_64-toolchain
metapackage, so you are using the msys toolchain rather than the mingw
one.



Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Eli Zaretskii
In reply to this post by Andy Moreton-3
> From: Andy Moreton <[hidden email]>
> Date: Fri, 13 Oct 2017 14:52:27 +0100
>
> >> MSYS2 is a rolling-release distribution, so any user who does not have
> >> an up to date installation would be well advised to update to current
> >> package versions before attempting to build emacs.
> >
> > I understand, but "advised" doesn't mean "forced", does it?
>
> No, in that things only get updated if you run pacman. However I thnk
> the first respone to "I have a problem" will be "update to current
> package versions".

I don't like requesting users to update all of their software just
because the bleeding edge has moved.  Let's not forget that sometimes
(albeit rarely) upgrading to the latest and greatest can bring bugs.

In this case, the payment for allowing older MSYS2 is very small: a
single sentence.  I think we should have that.



Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Noam Postavsky-2
On Fri, Oct 13, 2017 at 10:38 AM, Eli Zaretskii <[hidden email]> wrote:

> I don't like requesting users to update all of their software just
> because the bleeding edge has moved.  Let's not forget that sometimes
> (albeit rarely) upgrading to the latest and greatest can bring bugs.
>
> In this case, the payment for allowing older MSYS2 is very small: a
> single sentence.  I think we should have that.

I think the 'pacman -S msys2-launcher' should work for older MSYS2
without upgrading other packages, but then again, maybe not. There's
no practical way of testing older versions in the rolling release
model.
I suppose mentioning the bat file shouldn't be too much trouble (see attached).

v2-0001-nt-INSTALL.W64-Use-mingw64.exe-instead-of-mingw64.patch (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Eli Zaretskii
> From: Noam Postavsky <[hidden email]>
> Date: Fri, 13 Oct 2017 12:33:51 -0400
> Cc: Andy Moreton <[hidden email]>, [hidden email]
>
> +First we need to switch to the MinGW-w64 environment.  Exit the MSYS2
> +BASH console and run mingw64.exe in the C:\msys64 folder (if it's
> +missing, install it with 'pacman -S msys2-launcher'.  Or for very old
> +installs which have mingw64_shell.bat, use that instead), then cd
> +back to your Emacs source directory, e.g.:

The punctuation inside the parentheses needs fixing (it shouldn't
start a new sentence).  Otherwise, this is fine with me, thanks.



Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Noam Postavsky-2
On Fri, Oct 13, 2017 at 1:24 PM, Eli Zaretskii <[hidden email]> wrote:

> The punctuation inside the parentheses needs fixing (it shouldn't
> start a new sentence).  Otherwise, this is fine with me, thanks.

Hmm, can we get away with a semicolon then?

First we need to switch to the MinGW-w64 environment.  Exit the MSYS2
BASH console and run mingw64.exe in the C:\msys64 folder (if it's
missing, install it with 'pacman -S msys2-launcher'; or for very old
installs which have mingw64_shell.bat, use that instead), then cd
back to your Emacs source directory, e.g.:



Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Eli Zaretskii
> From: Noam Postavsky <[hidden email]>
> Date: Fri, 13 Oct 2017 13:51:21 -0400
> Cc: Andy Moreton <[hidden email]>, [hidden email]
>
> On Fri, Oct 13, 2017 at 1:24 PM, Eli Zaretskii <[hidden email]> wrote:
>
> > The punctuation inside the parentheses needs fixing (it shouldn't
> > start a new sentence).  Otherwise, this is fine with me, thanks.
>
> Hmm, can we get away with a semicolon then?

Yes, that's exactly what I meant.  Thanks.



Reply | Threaded
Open this post in threaded view
|

bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.

Noam Postavsky-2
In reply to this post by Noam Postavsky-2
Noam Postavsky <[hidden email]> writes:

> On Fri, Oct 13, 2017 at 10:09 AM, Vincent Belaïche
> <[hidden email]> wrote:
>
>> Please note that gcc -v makes this output even though my MSYSTEM envvar
>> expands to MINGW64.
>>
>> I think that the objective of the gcc -v is to discriminate between 32
>> and 64 bits, not between MINGW and MSYS. So, it seems that what we have
>> is an autoconf bug. Am I wrong ?
>
> I think it means you didn't install the mingw-w64-x86_64-toolchain
> metapackage, so you are using the msys toolchain rather than the mingw
> one.

Check the output of 'which gcc', it should be at /mingw64/bin/gcc.  If
it's /bin/gcc, or /usr/bin/gcc, then you are using the wrong gcc.



12