From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Pal Gloss <pcfeb0009@gmx.com>
Cc: 45303@debbugs.gnu.org
Subject: bug#45303: #45303 [feature/native-comp] building error on Windows
Date: Fri, 18 Dec 2020 16:02:20 +0000 [thread overview]
Message-ID: <xjfzh2bw19v.fsf@sdf.org> (raw)
In-Reply-To: <trinity-17a8ece9-bc7a-4624-ade8-9d8f06ab5701-1608290020567@3c-app-mailcom-bs08> (Pal Gloss's message of "Fri, 18 Dec 2020 12:13:40 +0100")
Pal Gloss <pcfeb0009@gmx.com> writes:
> Hi,
Hi Pal,
> Just in case this helps (sorry I did not have time to split up this into separate bug reports, but it will help [I hope]
> fix the problems encountered): here are the notes/hacks/command lines I used to build a recent gccemacs on my Win10
> machine with mingw64:
good to know is working even if with some hacking on it ;)
> #+begin_src shell :exports code
> git rev-parse HEAD feature/native-comp
> #+end_src
> : 682bd303470d4a0fcd2690aff6aa58fb720a8d41
> : 682bd303470d4a0fcd2690aff6aa58fb720a8d41
>
> #+begin_src shell :exports code
> pacman -S --needed base-devel \
> mingw-w64-x86_64-toolchain \
> mingw-w64-x86_64-xpm-nox \
> mingw-w64-x86_64-libtiff \
> mingw-w64-x86_64-giflib \
> mingw-w64-x86_64-libpng \
> mingw-w64-x86_64-libjpeg-turbo \
> mingw-w64-x86_64-librsvg \
> mingw-w64-x86_64-lcms2 \
> mingw-w64-x86_64-jansson \
> mingw-w64-x86_64-libxml2 \
> mingw-w64-x86_64-gnutls \
> mingw-w64-x86_64-zlib \
> mingw-w64-x86_64-harfbuzz \
> mingw-w64-x86_64-libgccjit
> PROCESSORS_TO_USE="3"
> EMACS_VERSION=emacs-native-comp
> ./autogen.sh
> # edit nt/epaths.nt to add PATH_REL_LOADSEARCH:
> grep -q PATH_REL_LOADSEARCH nt/epaths.nt || echo '#define PATH_REL_LOADSEARCH ""' >> nt/epaths.nt
This should be fixed by yesterday commits
> # patch to look for libgccjit-0.dll instead of libgcc.dll? lisp/term/w32-win.el & src/emacs.c
> sed -i -e 's/libgccjit.dll/libgccjit-0.dll/' lisp/term/w32-win.el
> sed -i -e 's/libgccjit.dll/libgccjit-0.dll/' src/emacs.c
I've really no windows knowledge to judge that, perhaps Eli will
comment. If these are correct fixes you should submit a patch for
those.
> # patch to avoid gcc_jit_global_set_initializer (crashes on my machine...; it
> # seems there is an interaction with the #pragma and the rest of the parsing
> # because the statement is incomplete?) and to adapt to (new) 5th parameter to
> # directory-files
> sed -i -e '/if (gcc_jit_global_set_initializer)/,/{/ {
> /#pragma GCC diagnostic pop/d
> /{/a #pragma GCC diagnostic pop
> }' \
> -e '/internal_condition_case_4/,/FOR_EACH/ {
> s/internal_condition_case_4/internal_condition_case_5/
> s/Qt, return_nil);/Qnil, Qt, return_nil);/
> }' \
> src/comp.c
which gcc version are you using?
> sed -i -e '/extern Lisp_Object internal_condition_case_4/a extern Lisp_Object internal_condition_case_5 (Lisp_Object
> (*) (Lisp_Object, Lisp_Object, Lisp_Object, Lisp_Object, Lisp_Object), Lisp_Object, Lisp_Object, Lisp_Object,
> Lisp_Object, Lisp_Object, Lisp_Object, Lisp_Object (*) (Lisp_Object));' src/lisp.h
> sed -i -e '/Like internal_condition_case_1 but call BFUN with ARG1, ARG2, ARG3, ARG4 as/ {
> s/ARG4 as/ARG4, ARG5 as/
> a its arguments. */
> a Lisp_Object
> a internal_condition_case_5 (Lisp_Object (*bfun) (Lisp_Object, Lisp_Object,
> a Lisp_Object, Lisp_Object,
> a Lisp_Object),
> a Lisp_Object arg1, Lisp_Object arg2,
> a Lisp_Object arg3, Lisp_Object arg4,
> a Lisp_Object arg5,
> a Lisp_Object handlers,
> a Lisp_Object (*hfun) (Lisp_Object))
> a {
> a struct handler *c = push_handler (handlers, CONDITION_CASE);
> a if (sys_setjmp (c->jmp))
> a {
> a Lisp_Object val = handlerlist->val;
> a clobbered_eassert (handlerlist == c);
> a handlerlist = handlerlist->next;
> a return hfun (val);
> a }
> a else
> a {
> a Lisp_Object val = bfun (arg1, arg2, arg3, arg4, arg5);
> a eassert (handlerlist == c);
> a handlerlist = c->next;
> a return val;
> a }
> a }
> a /* Like internal_condition_case_1 but call BFUN with ARG1, ARG2, ARG3, ARG4 as
> }' src/eval.c
> sed -i -e '/PATH_EXEC, 0);/ {
> s/.*/#ifdef WINDOWSNT/
> a /* On MS-Windows, PATH_EXEC normally starts with a literal
> a "%emacs_dir%", so it will never work without some tweaking. */
> a w32_relocate (PATH_EXEC),
> a #else
> a PATH_EXEC,
> a #endif
> a 0);
> }' src/callproc.c
> mkdir -p ../build
> cd ../build
> ../emacs/configure \
> --with-xml2 \
> --without-pop \
> --prefix="/home/cramaph1/$EMACS_VERSION/dest" \
> --without-compress-install \
> --without-dbus \
> --with-nativecomp \
> --with-modules 'CFLAGS=-O2 -g3' 'LIBGCCJIT=-lz -lgccjit'
> sed -i -e 's/^LIBGCCJIT = *$/LIBGCCJIT = -lz -lgccjit/' src/Makefile
> make -j"$PROCESSORS_TO_USE"
> make install
> #+end_src
Andrea
next prev parent reply other threads:[~2020-12-18 16:02 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 20:20 bug#45303: 28.0.50; [feature/native-comp] comp.c compilation error on Windows 10 =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-17 20:31 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-17 20:33 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-17 20:41 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-17 20:57 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-17 21:02 ` Eli Zaretskii
2020-12-17 21:10 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-17 21:27 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-17 21:41 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-18 13:28 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-18 16:06 ` Eli Zaretskii
2020-12-18 16:37 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-18 19:35 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-18 21:26 ` Eli Zaretskii
2020-12-19 0:57 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-19 5:38 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-19 8:04 ` Eli Zaretskii
2020-12-18 19:40 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-18 20:49 ` Eli Zaretskii
2020-12-21 9:48 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-19 17:56 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-18 11:13 ` bug#45303: #45303 [feature/native-comp] building error on Windows Pal Gloss
2020-12-18 16:02 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-12-18 21:22 ` Eli Zaretskii
2020-12-18 22:21 ` Pal Gloss
2020-12-19 7:57 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-19 14:35 ` Andy Moreton
2020-12-19 16:15 ` Eli Zaretskii
2020-12-19 17:15 ` Andy Moreton
2020-12-19 17:37 ` Eli Zaretskii
2020-12-19 21:39 ` Andy Moreton
2020-12-19 18:07 ` Pal Gloss
2020-12-19 20:40 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-20 11:22 ` Andy Moreton
2020-12-20 18:58 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-20 19:11 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-21 0:53 ` Andy Moreton
2020-12-21 8:02 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-21 8:09 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-21 17:41 ` Andy Moreton
2020-12-20 16:23 ` Pal Gloss
2020-12-20 19:07 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-21 10:10 ` Pal Gloss
2020-12-21 12:08 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-21 22:46 ` Andy Moreton
2020-12-22 8:47 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-22 19:41 ` Andy Moreton
2020-12-21 16:21 ` Eli Zaretskii
2020-12-18 22:25 ` Pal Gloss
2020-12-19 19:08 ` bug#45303: #45303 [feature/native-comp] building error on Windows ... strsignal in msys2/mingw64 Pal Gloss
2020-12-19 19:29 ` Eli Zaretskii
2020-12-20 16:15 ` Pal Gloss
2020-12-19 23:04 ` bug#45303: 28.0.50; [feature/native-comp] comp.c compilation error on Windows 10 =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-20 2:31 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-20 8:38 ` Michael Albinus
2020-12-20 9:49 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-20 19:10 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-20 19:46 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-20 20:04 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-20 16:32 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-21 18:02 ` =?UTF-8?Q?Li=C4=81u, _?= Kiong-Gē 廖宮毅
2020-12-22 15:47 ` bug#45303: #45303 [feature/native-comp] building error on Windows gliao.tw--- via
2020-12-22 19:15 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-22 19:48 ` gliao.tw--- via
2020-12-22 20:09 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-22 20:15 ` gliao.tw--- via
2020-12-22 20:21 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-22 20:39 ` Eli Zaretskii
2020-12-23 7:01 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-26 14:02 ` edouard debry
2020-12-26 14:24 ` Eli Zaretskii
2020-12-26 14:58 ` edouard debry
2020-12-26 15:12 ` Eli Zaretskii
2021-01-06 20:37 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-22 19:46 ` Andy Moreton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xjfzh2bw19v.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=45303@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=pcfeb0009@gmx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).