From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: building Emacs on Msys2/mingw32
Date: Tue, 09 Sep 2014 00:53:43 +0200 [thread overview]
Message-ID: <87bnqp7mh4.fsf@wanadoo.es> (raw)
In-Reply-To: 540E2585.5070606@alice.it
Angelo Graziosi <angelo.graziosi@alice.it> writes:
> Óscar Fuentes wrote:
>> All this and the remaining removed text is unnecessary if you use
>> mingw32_shell.bat
>
> Hmm... This was what I thought. I build the W64 binaries of Emacs, and
> I DO use mingw64_shell.bat, where:
>
[snip]
> and I build with
>
> $ ./autogen.sh
> $ ./configure --prefix=/Emacs --with-wide-int
> --build=x86_64-w64-mingw32 --without-imagemagick
> 'CFLAGS=-I/mingw64/include/noX -Ofast -g0 -pipe' LDFLAGS=-pipe
>
> $ make -j3
>
>
> If I remove the "--build=x86_64-w64-mingw32" option to configure, the
> build is configure for x86_64-pc-mingw64,
>
> [...]
> Configured for `x86_64-pc-mingw64'.
[snip]
> and 'make -j3' fails at some point.. Instead, with that configure
> option, the build is configure for 'x86_64-w64-mingw32' and it is
> completed successfully...
Either the configure script does not handle the target triple
x86_64-pc-mingw64 correctly, or that target triple is incorrect (IIRC
the target triple is inferred by a script `configure' calls:
build-aux/config.guess.)
> So, may you explain how you build Emacs on MSYS2?
I don't build Emacs 64 bits on Windows, just the 32 bit build (as the OP
does). It works fine without passing any parameter to `configure'.
next prev parent reply other threads:[~2014-09-08 22:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 21:54 building Emacs on Msys2/mingw32 Angelo Graziosi
2014-09-08 22:53 ` Óscar Fuentes [this message]
2014-09-09 13:42 ` Eli Zaretskii
2014-09-09 17:53 ` Angelo Graziosi
2014-09-09 18:11 ` Eli Zaretskii
2014-09-09 18:15 ` Eli Zaretskii
2014-09-09 19:50 ` Fabrice Popineau
-- strict thread matches above, loose matches on Subject: below --
2014-09-08 15:54 Stephen Leake
2014-09-08 20:14 ` Óscar Fuentes
2014-09-09 5:00 ` Stephen Leake
2014-09-09 10:39 ` Chris Zheng
2014-09-09 13:58 ` Stephen Leake
2014-09-09 13:48 ` Eli Zaretskii
2014-09-09 13:28 ` Eli Zaretskii
2014-09-09 22:03 ` Stephen Leake
2014-09-10 3:22 ` 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
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=87bnqp7mh4.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--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).