From: "Liāu, Kiong-Gē 廖宮毅" <gongyi.liao@gmail.com>
To: emacs-devel@gnu.org
Subject: Native-comp branch compilation error on Windows
Date: Wed, 16 Dec 2020 19:44:05 -0600 [thread overview]
Message-ID: <CALKwrMCv2FFQ4JEV_pu_2cP3fC6PsF1P4GP3s0587ty+TWaP_g@mail.gmail.com> (raw)
Hi,
I used last updated Msys2 as 2020-12-16 to install mingw64-x86_64
version (10.2) of gcc and libgccjit to compile native-comp branch on
Windows 10.
I configured the build with flag --with-nativecomp, while compile it,
I got the following error message:
comp.c: In function 'Fcomp_el_to_eln_filename':
comp.c:4110:36: error: expected ')' before 'PATH_REL_LOADSEARCH'
4110 | Fregexp_quote (build_string ("/" PATH_REL_LOADSEARCH "/")));
| ^~~~~~~~~~~~~~~~~~~~
| )
comp.c: In function 'Fcomp__compile_ctxt_to_file':
comp.c:4458:12: warning: unused variable 'oldset' [-Wunused-variable]
4458 | sigset_t oldset;
| ^~~~~~
comp.c: In function 'eln_load_path_final_clean_up':
comp.c:4621:29: warning: passing argument 1 of
'internal_condition_case_4' from incompatible pointer type
[-Wincompatible-pointer-types]
4621 | internal_condition_case_4 (Fdirectory_files,
| ^~~~~~~~~~~~~~~~
| |
| struct Lisp_X * (*)(struct Lisp_X
*, struct Lisp_X *, struct Lisp_X *, struct Lisp_X *, struct Lisp_X *)
In file included from comp.c:23:
lisp.h:4160:47: note: expected 'struct Lisp_X * (*)(struct Lisp_X *,
struct Lisp_X *, struct Lisp_X *, struct Lisp_X *)' but argument is of
type 'struct Lisp_X * (*)(struct Lisp_X *, struct Lisp_X *, struct
Lisp_X *, struct Lisp_X *, struct Lisp_X *)'
4160 | extern Lisp_Object internal_condition_case_4 (Lisp_Object (*)
(Lisp_Object, Lisp_Object, Lisp_Object, Lisp_Object), Lisp_Object,
Lisp_Object, Lisp_Object, Lisp_Object, Lisp_Object, Lisp_Object (*)
(Lisp_Object));
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[1]: *** [Makefile:410: comp.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/home/VWinUser0/Downloads/emacs/native-comp/src'
make: *** [Makefile:433: src] Error 2
However, with exactly the same emacs source code and configuration,
the compilation on Linux (Debian testing, gcc/gccjit 10.2) went well
without any issue.
Should I pass some special flags in configure or compilers to build
the native-comp branch on Windows?
Thanks,
Kiong-Ge.
next reply other threads:[~2020-12-17 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 1:44 Liāu, Kiong-Gē 廖宮毅 [this message]
2020-12-17 19:51 ` Native-comp branch compilation error on Windows Andrea Corallo via Emacs development discussions.
2020-12-17 20:43 ` Eli Zaretskii
2020-12-17 20:48 ` Liāu, Kiong-Gē 廖宮毅
2020-12-17 21:00 ` Eli Zaretskii
2020-12-17 21:06 ` Liāu, Kiong-Gē 廖宮毅
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=CALKwrMCv2FFQ4JEV_pu_2cP3fC6PsF1P4GP3s0587ty+TWaP_g@mail.gmail.com \
--to=gongyi.liao@gmail.com \
--cc=emacs-devel@gnu.org \
/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).