* Re: windows build help
@ 2017-10-14 8:16 Angelo Graziosi
2017-10-14 11:16 ` Phillip Lord
0 siblings, 1 reply; 15+ messages in thread
From: Angelo Graziosi @ 2017-10-14 8:16 UTC (permalink / raw)
To: emacs-devel
Phillip Lord wrote:
> But I do the x86_64 building using the MINGW64 shell
> (i.e. C:\msys64\mingw64.exe) and the i686 using MINGW32
in my script I added this:
MSYSTEM="MINGW64"
PATH="/mingw64/bin:$PATH"
Also this should work:
MSYSTEM=MINGW64 PATH="/mingw64/bin:$PATH" ~/emacs-w64-build.sh
> the entire build takes about an hour or two
On which machine? Here (an Athlon X2, 10 years old), with 'make -j3', the build [1] takes about 35-40 minutes [2].
Ciao,
Angelo.
-----
[1] From http://git.savannah.gnu.org/cgit/emacs.git/snapshot/emacs-master.tar.gz
[2] Download of [1], unpacking, build, and tar.xz creation.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-14 8:16 windows build help Angelo Graziosi
@ 2017-10-14 11:16 ` Phillip Lord
0 siblings, 0 replies; 15+ messages in thread
From: Phillip Lord @ 2017-10-14 11:16 UTC (permalink / raw)
To: Angelo Graziosi; +Cc: emacs-devel
Angelo Graziosi <angelo.g0@libero.it> writes:
> Phillip Lord wrote:
>
>> But I do the x86_64 building using the MINGW64 shell
>> (i.e. C:\msys64\mingw64.exe) and the i686 using MINGW32
>
> in my script I added this:
>
> MSYSTEM="MINGW64"
> PATH="/mingw64/bin:$PATH"
>
> Also this should work:
>
> MSYSTEM=MINGW64 PATH="/mingw64/bin:$PATH" ~/emacs-w64-build.sh
>
>> the entire build takes about an hour or two
>
> On which machine? Here (an Athlon X2, 10 years old), with 'make -j3',
> the build [1] takes about 35-40 minutes [2].
The majority of the time is the elc compilation. So, the first build
takes a long time, second much (much) less.
There is also quite a lot of baggage on top of this. After the zip files
have been build, I have to unzip them, so I check they run cleanly. This
takes around 5 minutes per zip. For Emacs-26, I'm making four zips. Then
the uploads. I normally do it over two days.
Phil
^ permalink raw reply [flat|nested] 15+ messages in thread
* bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
@ 2017-09-25 20:02 Vincent Belaïche
2017-09-27 18:36 ` Glenn Morris
0 siblings, 1 reply; 15+ messages in thread
From: Vincent Belaïche @ 2017-09-25 20:02 UTC (permalink / raw)
To: 28601; +Cc: Vincent Belaïche
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 bug-gnu-emacs@gnu.org.
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\a
[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
^ permalink raw reply [flat|nested] 15+ messages in thread
* bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
2017-09-25 20:02 bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems Vincent Belaïche
@ 2017-09-27 18:36 ` Glenn Morris
2017-09-27 19:07 ` Vincent Belaïche
0 siblings, 1 reply; 15+ messages in thread
From: Glenn Morris @ 2017-09-27 18:36 UTC (permalink / raw)
To: Vincent Belaïche; +Cc: 28601
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?
^ permalink raw reply [flat|nested] 15+ messages in thread
* bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
2017-09-27 18:36 ` Glenn Morris
@ 2017-09-27 19:07 ` Vincent Belaïche
2017-09-27 21:37 ` Glenn Morris
0 siblings, 1 reply; 15+ messages in thread
From: Vincent Belaïche @ 2017-09-27 19:07 UTC (permalink / raw)
To: Glenn Morris; +Cc: 28601
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
2017-09-27 19:07 ` Vincent Belaïche
@ 2017-09-27 21:37 ` Glenn Morris
2017-09-28 13:10 ` Andy Moreton
0 siblings, 1 reply; 15+ messages in thread
From: Glenn Morris @ 2017-09-27 21:37 UTC (permalink / raw)
To: Vincent Belaïche; +Cc: 28601
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
2017-09-27 21:37 ` Glenn Morris
@ 2017-09-28 13:10 ` Andy Moreton
2017-09-29 9:37 ` Eli Zaretskii
0 siblings, 1 reply; 15+ messages in thread
From: Andy Moreton @ 2017-09-28 13:10 UTC (permalink / raw)
To: 28601
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
^ permalink raw reply [flat|nested] 15+ messages in thread
* bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
2017-09-28 13:10 ` Andy Moreton
@ 2017-09-29 9:37 ` Eli Zaretskii
2017-10-12 23:06 ` Noam Postavsky
0 siblings, 1 reply; 15+ messages in thread
From: Eli Zaretskii @ 2017-09-29 9:37 UTC (permalink / raw)
To: Andy Moreton; +Cc: 28601
> From: Andy Moreton <andrewjmoreton@gmail.com>
> 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.
^ permalink raw reply [flat|nested] 15+ messages in thread
* bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
2017-09-29 9:37 ` Eli Zaretskii
@ 2017-10-12 23:06 ` Noam Postavsky
2017-10-13 6:41 ` Eli Zaretskii
0 siblings, 1 reply; 15+ messages in thread
From: Noam Postavsky @ 2017-10-12 23:06 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 28601, Andy Moreton, Vincent Belaïche
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
On Fri, Sep 29, 2017 at 5:37 AM, Eli Zaretskii <eliz@gnu.org> 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.
[-- Attachment #2: 0001-nt-INSTALL.W64-Use-mingw64.exe-instead-of-mingw64_sh.patch --]
[-- Type: application/octet-stream, Size: 1037 bytes --]
From fc6083a57cea4f9dff3c865f2185902c337d4cf5 Mon Sep 17 00:00:00 2001
From: Noam Postavsky <npostavs@gmail.com>
Date: Thu, 12 Oct 2017 19:01:37 -0400
Subject: [PATCH] * nt/INSTALL.W64: Use mingw64.exe instead of
mingw64_shell.bat.
---
nt/INSTALL.W64 | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/nt/INSTALL.W64 b/nt/INSTALL.W64
index 841660b..c651a21 100644
--- a/nt/INSTALL.W64
+++ b/nt/INSTALL.W64
@@ -125,8 +125,9 @@ put the Emacs source into C:\emacs\emacs-25:
Now you're ready to build and install Emacs with autogen, configure, make,
and make install.
-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.:
cd /c/emacs/emacs-25
--
2.6.2.windows.1
^ permalink raw reply related [flat|nested] 15+ messages in thread
* bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
2017-10-12 23:06 ` Noam Postavsky
@ 2017-10-13 6:41 ` Eli Zaretskii
2017-10-13 10:14 ` Andy Moreton
0 siblings, 1 reply; 15+ messages in thread
From: Eli Zaretskii @ 2017-10-13 6:41 UTC (permalink / raw)
To: Noam Postavsky; +Cc: 28601, andrewjmoreton, vincent.belaiche
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Thu, 12 Oct 2017 19:06:56 -0400
> Cc: Andy Moreton <andrewjmoreton@gmail.com>, 28601@debbugs.gnu.org,
> Vincent Belaïche <vincent.belaiche@gmail.com>
>
> -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.
^ permalink raw reply [flat|nested] 15+ messages in thread
* bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems.
2017-10-13 6:41 ` Eli Zaretskii
@ 2017-10-13 10:14 ` Andy Moreton
2017-10-13 18:52 ` windows build help Phillip Lord
0 siblings, 1 reply; 15+ messages in thread
From: Andy Moreton @ 2017-10-13 10:14 UTC (permalink / raw)
To: 28601
On Fri 13 Oct 2017, Eli Zaretskii wrote:
>> From: Noam Postavsky <npostavs@users.sourceforge.net>
>> Date: Thu, 12 Oct 2017 19:06:56 -0400
>> Cc: Andy Moreton <andrewjmoreton@gmail.com>, 28601@debbugs.gnu.org,
>> Vincent Belaïche <vincent.belaiche@gmail.com>
>>
>> -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
^ permalink raw reply [flat|nested] 15+ messages in thread
* windows build help
2017-10-13 10:14 ` Andy Moreton
@ 2017-10-13 18:52 ` Phillip Lord
2017-10-13 19:36 ` Óscar Fuentes
` (2 more replies)
0 siblings, 3 replies; 15+ messages in thread
From: Phillip Lord @ 2017-10-13 18:52 UTC (permalink / raw)
To: Emacs-Devel devel
I was just reading 28601@debbugs.gnu.org. I have a slightly related
problem and wonder if anyone could help.
Currently, I am building the windows binaries for Emacs using an
out-of-source build with a directory structure like this:
git/emacs-26.0.50
build/emacs-26.0.50/x86_64
build/emacs-26.0.50/i686
install/emacs-26.0.50/x86_64
install/emacs-26.0.50/i686
This works nicely, but some of the process is manual. I wanted to script
everything up to and including the creation of the final zip files --
currently, the entire build takes about an hour or two.
But I do the x86_64 building using the MINGW64 shell
(i.e. C:\msys64\mingw64.exe) and the i686 using MINGW32
(i.e. C:\msys64\mingw64.exe). You might have thought I could just used
one -- the build for the i686 would just be cross compiling. But, this
doesn't work because I get this from ./configure:
checking for struct ifreq.ifr_addr.sa_len... no
checking whether gcc understands -MMD -MF... no
checking for long file names... yes
checking for X... no
checking whether Windows API headers are recent enough... no
configure: error: the Windows API headers are too old to support this build.
So, I cannot do both builds with a single command -- I have to come back
in the middle. I don't really understand the difference between the two
shells nor why I get this error.
Another solution would be to run both builds in parallel; this fails,
unfortunately, because the "out-of-source" build is not entirely out of
source -- the .elc files are created in-source. If I launch both a 64
and 32 bit build at the same time, they fight for whole compiles what,
until one or both crash.
It's not a major issue, but I'd quite like to start providing emacs-27
snapshots every couple of weeks. It's not going to happen, if it takes
too much effort.
Any thoughts welcome.
Phil
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-13 18:52 ` windows build help Phillip Lord
@ 2017-10-13 19:36 ` Óscar Fuentes
2017-10-13 19:38 ` Stephen Leake
2017-10-13 19:47 ` Noam Postavsky
2 siblings, 0 replies; 15+ messages in thread
From: Óscar Fuentes @ 2017-10-13 19:36 UTC (permalink / raw)
To: emacs-devel
phillip.lord@russet.org.uk (Phillip Lord) writes:
> So, I cannot do both builds with a single command -- I have to come back
> in the middle. I don't really understand the difference between the two
> shells nor why I get this error.
Look at the scripts that start each shell. They setup some environment
variables. Mimic that on your script and you should be fine.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-13 18:52 ` windows build help Phillip Lord
2017-10-13 19:36 ` Óscar Fuentes
@ 2017-10-13 19:38 ` Stephen Leake
2017-10-14 11:07 ` Phillip Lord
2017-10-13 19:47 ` Noam Postavsky
2 siblings, 1 reply; 15+ messages in thread
From: Stephen Leake @ 2017-10-13 19:38 UTC (permalink / raw)
To: emacs-devel
phillip.lord@russet.org.uk (Phillip Lord) writes:
> Another solution would be to run both builds in parallel; this fails,
> unfortunately, because the "out-of-source" build is not entirely out of
> source -- the .elc files are created in-source. If I launch both a 64
> and 32 bit build at the same time, they fight for whole compiles what,
> until one or both crash.
Have two source checkouts. then you could also build in-source, although
I doubt that makes much difference.
--
-- Stephe
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-13 19:38 ` Stephen Leake
@ 2017-10-14 11:07 ` Phillip Lord
2017-10-14 15:15 ` Stephen Leake
0 siblings, 1 reply; 15+ messages in thread
From: Phillip Lord @ 2017-10-14 11:07 UTC (permalink / raw)
To: Stephen Leake; +Cc: emacs-devel
Stephen Leake <stephen_leake@stephe-leake.org> writes:
> phillip.lord@russet.org.uk (Phillip Lord) writes:
>
>> Another solution would be to run both builds in parallel; this fails,
>> unfortunately, because the "out-of-source" build is not entirely out of
>> source -- the .elc files are created in-source. If I launch both a 64
>> and 32 bit build at the same time, they fight for whole compiles what,
>> until one or both crash.
>
> Have two source checkouts. then you could also build in-source, although
> I doubt that makes much difference.
I thought about that, but the reason against it is that it takes much
longer, because I have to build the elc twice.
Phil
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-14 11:07 ` Phillip Lord
@ 2017-10-14 15:15 ` Stephen Leake
2017-10-14 15:26 ` Phillip Lord
` (2 more replies)
0 siblings, 3 replies; 15+ messages in thread
From: Stephen Leake @ 2017-10-14 15:15 UTC (permalink / raw)
To: emacs-devel
phillip.lord@russet.org.uk (Phillip Lord) writes:
> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>
>> phillip.lord@russet.org.uk (Phillip Lord) writes:
>>
>>> Another solution would be to run both builds in parallel; this fails,
>>> unfortunately, because the "out-of-source" build is not entirely out of
>>> source -- the .elc files are created in-source. If I launch both a 64
>>> and 32 bit build at the same time, they fight for whole compiles what,
>>> until one or both crash.
>>
>> Have two source checkouts. then you could also build in-source, although
>> I doubt that makes much difference.
>
> I thought about that, but the reason against it is that it takes much
> longer, because I have to build the elc twice.
Hmm. You are implying that the elc built for 32 bit emacs are identical
to the elc built for 64 bit emacs.
Is that true? I would have guessed that most objects are either
32 bit or 64 bit; elisp manual 3.1 says the integer range depends on the
machine, and pointers should also.
If they are the same, then you should be able to write a script that
does:
1) parallel make to build elc using 32 bit
2) parallel make to build everything else, both 32 bit and 64 bit.
--
-- Stephe
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-14 15:15 ` Stephen Leake
@ 2017-10-14 15:26 ` Phillip Lord
2017-10-14 15:31 ` Eli Zaretskii
2017-10-14 23:04 ` Paul Eggert
2 siblings, 0 replies; 15+ messages in thread
From: Phillip Lord @ 2017-10-14 15:26 UTC (permalink / raw)
To: Stephen Leake; +Cc: emacs-devel
Stephen Leake <stephen_leake@stephe-leake.org> writes:
> phillip.lord@russet.org.uk (Phillip Lord) writes:
>
>> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>>
>>> phillip.lord@russet.org.uk (Phillip Lord) writes:
>>>
>>>> Another solution would be to run both builds in parallel; this fails,
>>>> unfortunately, because the "out-of-source" build is not entirely out of
>>>> source -- the .elc files are created in-source. If I launch both a 64
>>>> and 32 bit build at the same time, they fight for whole compiles what,
>>>> until one or both crash.
>>>
>>> Have two source checkouts. then you could also build in-source, although
>>> I doubt that makes much difference.
>>
>> I thought about that, but the reason against it is that it takes much
>> longer, because I have to build the elc twice.
>
> Hmm. You are implying that the elc built for 32 bit emacs are identical
> to the elc built for 64 bit emacs.
>
> Is that true? I would have guessed that most objects are either
> 32 bit or 64 bit; elisp manual 3.1 says the integer range depends on the
> machine, and pointers should also.
Yes, I believe that they are. In fact, the source tar-ball includes the
ELC files, when it's possible to build from source on many different
platforms.
I use to build both 32 and 64 totally form source (i.e. without ELC),
but haven't done for I think all of Emacs-25.
> If they are the same, then you should be able to write a script that
> does:
>
> 1) parallel make to build elc using 32 bit
> 2) parallel make to build everything else, both 32 bit and 64 bit.
I have this now, thanks to comments in this thread. I do, parallel build
of 64 bit, then parallel build of 32 bit. The ELC build happens during
the 64, although it could happen either way.
Phil
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-14 15:15 ` Stephen Leake
2017-10-14 15:26 ` Phillip Lord
@ 2017-10-14 15:31 ` Eli Zaretskii
2017-10-14 23:04 ` Paul Eggert
2 siblings, 0 replies; 15+ messages in thread
From: Eli Zaretskii @ 2017-10-14 15:31 UTC (permalink / raw)
To: Stephen Leake; +Cc: emacs-devel
> From: Stephen Leake <stephen_leake@stephe-leake.org>
> Date: Sat, 14 Oct 2017 10:15:41 -0500
>
> Hmm. You are implying that the elc built for 32 bit emacs are identical
> to the elc built for 64 bit emacs.
>
> Is that true?
Yes.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-14 15:15 ` Stephen Leake
2017-10-14 15:26 ` Phillip Lord
2017-10-14 15:31 ` Eli Zaretskii
@ 2017-10-14 23:04 ` Paul Eggert
2017-10-16 1:53 ` Richard Stallman
2 siblings, 1 reply; 15+ messages in thread
From: Paul Eggert @ 2017-10-14 23:04 UTC (permalink / raw)
To: Stephen Leake, emacs-devel
Stephen Leake wrote:
> You are implying that the elc built for 32 bit emacs are identical
> to the elc built for 64 bit emacs.
Although one can write Elisp code that compiles to different .elc files
depending whether the compiling Emacs is built for a 32 or 64 bit machine, such
Elisp code is unportable and the GNU Emacs source code does not do that, as far
as I know. (It might be nice if we routinely tested for such portability bugs.)
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-14 23:04 ` Paul Eggert
@ 2017-10-16 1:53 ` Richard Stallman
2017-10-16 6:49 ` Paul Eggert
0 siblings, 1 reply; 15+ messages in thread
From: Richard Stallman @ 2017-10-16 1:53 UTC (permalink / raw)
To: Paul Eggert; +Cc: stephen_leake, emacs-devel
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Although one can write Elisp code that compiles to different .elc files
> depending whether the compiling Emacs is built for a 32 or 64 bit machine,
Just for curiosity's sake, would anyone like to tell me what circumstances
this happens in?
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-16 1:53 ` Richard Stallman
@ 2017-10-16 6:49 ` Paul Eggert
2017-10-16 13:54 ` Stefan Monnier
0 siblings, 1 reply; 15+ messages in thread
From: Paul Eggert @ 2017-10-16 6:49 UTC (permalink / raw)
To: rms; +Cc: stephen_leake, emacs-devel
> > one can write Elisp code that compiles to different .elc files
> > depending whether the compiling Emacs is built for a 32 or 64 bit machine,
>
> Just for curiosity's sake, would anyone like to tell me what circumstances
> this happens in?
For example, given this source code:
(defconst x (* 32768 32768))
On a 64-bit machine, byte-compiling generates an .elc file containing this:
(defconst x 1073741824)
On a 32-bit machine, byte-compiling the same source code generates an .elc file
containing this instead:
(defconst x 0)
due to multiplication overflow in this Emacs's integers, which use 30-bit two's
complement. Each .elc file is correct for the Emacs it is built with, but
incorrect for the other Emacs.
GNU Emacs source code should not do this sort of thing, since the .elc files
distributed in its tarballs are supposed to be portable.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-13 18:52 ` windows build help Phillip Lord
2017-10-13 19:36 ` Óscar Fuentes
2017-10-13 19:38 ` Stephen Leake
@ 2017-10-13 19:47 ` Noam Postavsky
2017-10-14 11:09 ` Phillip Lord
2 siblings, 1 reply; 15+ messages in thread
From: Noam Postavsky @ 2017-10-13 19:47 UTC (permalink / raw)
To: Phillip Lord; +Cc: Emacs-Devel devel
On Fri, Oct 13, 2017 at 2:52 PM, Phillip Lord
<phillip.lord@russet.org.uk> wrote:
> But I do the x86_64 building using the MINGW64 shell
> (i.e. C:\msys64\mingw64.exe) and the i686 using MINGW32
> (i.e. C:\msys64\mingw64.exe). You might have thought I could just used
> one -- the build for the i686 would just be cross compiling.
AFAIK, emacs doesn't support cross compiling.
> So, I cannot do both builds with a single command -- I have to come back
> in the middle. I don't really understand the difference between the two
> shells nor why I get this error.
I think the only difference is PATH has /mingw32/bin or /mingw64/bin,
and MSYSTEM is MINGW32 or MINGW64
At least for me, after doing
PATH=/mingw32/bin:$PATH
MSYSTEM=MINGW32
in a mingw64 shell, doing ./configure succeeds and I end up with a 32bit emacs.
^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: windows build help
2017-10-13 19:47 ` Noam Postavsky
@ 2017-10-14 11:09 ` Phillip Lord
0 siblings, 0 replies; 15+ messages in thread
From: Phillip Lord @ 2017-10-14 11:09 UTC (permalink / raw)
To: Noam Postavsky; +Cc: Emacs-Devel devel
Noam Postavsky <npostavs@users.sourceforge.net> writes:
> On Fri, Oct 13, 2017 at 2:52 PM, Phillip Lord
> <phillip.lord@russet.org.uk> wrote:
>
>> But I do the x86_64 building using the MINGW64 shell
>> (i.e. C:\msys64\mingw64.exe) and the i686 using MINGW32
>> (i.e. C:\msys64\mingw64.exe). You might have thought I could just used
>> one -- the build for the i686 would just be cross compiling.
>
> AFAIK, emacs doesn't support cross compiling.
I assumed that only GCC needed to do this (assuming that the emacs
produced can run on the current system).
>
>> So, I cannot do both builds with a single command -- I have to come back
>> in the middle. I don't really understand the difference between the two
>> shells nor why I get this error.
>
> I think the only difference is PATH has /mingw32/bin or /mingw64/bin,
> and MSYSTEM is MINGW32 or MINGW64
>
> At least for me, after doing
>
> PATH=/mingw32/bin:$PATH
> MSYSTEM=MINGW32
>
> in a mingw64 shell, doing ./configure succeeds and I end up with a
> 32bit emacs.
Yep, that's all you need. Thank you very much!
Phil
^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2017-10-16 13:54 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-10-14 8:16 windows build help Angelo Graziosi
2017-10-14 11:16 ` Phillip Lord
-- strict thread matches above, loose matches on Subject: below --
2017-09-25 20:02 bug#28601: 26.0.50; configure: error: Emacs does not support 'x86_64-pc-msys' systems Vincent Belaïche
2017-09-27 18:36 ` Glenn Morris
2017-09-27 19:07 ` Vincent Belaïche
2017-09-27 21:37 ` Glenn Morris
2017-09-28 13:10 ` Andy Moreton
2017-09-29 9:37 ` Eli Zaretskii
2017-10-12 23:06 ` Noam Postavsky
2017-10-13 6:41 ` Eli Zaretskii
2017-10-13 10:14 ` Andy Moreton
2017-10-13 18:52 ` windows build help Phillip Lord
2017-10-13 19:36 ` Óscar Fuentes
2017-10-13 19:38 ` Stephen Leake
2017-10-14 11:07 ` Phillip Lord
2017-10-14 15:15 ` Stephen Leake
2017-10-14 15:26 ` Phillip Lord
2017-10-14 15:31 ` Eli Zaretskii
2017-10-14 23:04 ` Paul Eggert
2017-10-16 1:53 ` Richard Stallman
2017-10-16 6:49 ` Paul Eggert
2017-10-16 13:54 ` Stefan Monnier
2017-10-13 19:47 ` Noam Postavsky
2017-10-14 11:09 ` Phillip Lord
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.