From: Angelo Graziosi <angelo.g0@libero.it>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Master fails to build on Windows
Date: Fri, 1 Nov 2019 19:11:22 +0100 (CET) [thread overview]
Message-ID: <1212616481.195226.1572631882704@mail1.libero.it> (raw)
In-Reply-To: <83lfszlh96.fsf@gnu.org>
> Il 1 novembre 2019 alle 16.59 Eli Zaretskii ha scritto:
>
> So you don't invoke configure and make, but instead run a script
> called makepkg-mingw? And D_FORTIFY_SOURCE=2 is set by that script?
No no, my script (emacs-w64-build.sh) downloads the source, run autogen.sh and
eval "${emacs_build_env}" ./configure --prefix="/${PREFIXNAME}" \
--build=x86_64-w64-mingw32 \
--without-imagemagick \
--without-dbus \
--without-pop \
--with-modules
make ${MAKE_OPT}
where
emacs_build_env is, basically,
CPPFLAGS="-D_FORTIFY_SOURCE=2 -D__USE_MINGW_ANSI_STDIO=1" \
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe"
MAKE_OPT is, basically, '-j 6'. Now I removed '-D_FORTIFY_SOURCE=2'.
Then, the script creates the .7z package.
The script 'makepkg-mingw' belongs to MSYS2 installation. If you remember, MSYS2 uses PKGBUILD scripts as in ArchLinux and 'makepkg-mingw' is used to build MinGW packages (there is also a 'makepkg' script to build _native_ MSYS2 packages). See https://github.com/msys2/msys2/wiki/Creating-packages#building.
next prev parent reply other threads:[~2019-11-01 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 9:56 Master fails to build on Windows Angelo Graziosi
2019-11-01 10:31 ` Eli Zaretskii
2019-11-01 10:41 ` Angelo Graziosi
2019-11-01 11:27 ` Angelo Graziosi
2019-11-01 12:47 ` Angelo Graziosi
2019-11-01 12:58 ` Eli Zaretskii
2019-11-01 15:12 ` Angelo Graziosi
2019-11-01 15:59 ` Eli Zaretskii
2019-11-01 18:11 ` Angelo Graziosi [this message]
2019-11-01 18:54 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1212616481.195226.1572631882704@mail1.libero.it \
--to=angelo.g0@libero.it \
--cc=eliz@gnu.org \
--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 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.