From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: emacs-devel@gnu.org
Subject: Re: building Emacs on Msys2/mingw32
Date: Wed, 10 Sep 2014 06:22:52 +0300 [thread overview]
Message-ID: <83lhps9n1v.fsf@gnu.org> (raw)
In-Reply-To: <85ha0gwixf.fsf@stephe-leake.org>
> From: Stephen Leake <stephen_leake@stephe-leake.org>
> Date: Tue, 09 Sep 2014 17:03:24 -0500
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Stephen Leake <stephen_leake@stephe-leake.org>
> >> Date: Mon, 08 Sep 2014 10:54:26 -0500
> >>
> >> I had to override the guessed build machine on the configure line:
> >>
> >> $ ./configure --build=i686-pc-mingw32 --prefix=/mingw32
> >>
> >> config.guess returns x86_64-pc-msys; configure rejects this.
> >>
> >> x86_64-pc-msys is the correct host identifier
> >
> > No, it isn't: it identifies an MSYS program, not a MinGW program.
>
> Yes, and the _host_ is MSYS bash.
>
> The _build_ (ie target) is MinGW. Which is why I used --build, not --host.
Since MSYS2's main purpose is to build MinGW programs, it should
produce a MinGW targeted triplet by default. At least that's what
MSYS does.
next prev parent reply other threads:[~2014-09-10 3:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 15:54 building Emacs on Msys2/mingw32 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-08 21:54 Angelo Graziosi
2014-09-08 22:53 ` Óscar Fuentes
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
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=83lhps9n1v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen_leake@stephe-leake.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.