From: Eli Zaretskii <eliz@gnu.org>
To: ilya@math.berkeley.edu
Cc: 19989@debbugs.gnu.org
Subject: bug#19989: 25.0.50; Build instructions on Windows
Date: Fri, 06 Mar 2015 12:08:00 +0200 [thread overview]
Message-ID: <83h9tyo2v3.fsf@gnu.org> (raw)
In-Reply-To: <83lhjao7fr.fsf@gnu.org>
> Date: Fri, 06 Mar 2015 10:29:12 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 19989@debbugs.gnu.org
>
> > Of course they do. configure did not work (since the gcc found on
> > path was not MINGW one).
>
> So that's the problem: you installed the MSYS GCC (and probably the
> whole MSYS development environment), something one shouldn't do for
> building MinGW programs.
Or maybe I again misunderstood, and the GCC found first on PATH was
the Cygwin GCC? Then that'd be the "don't mix Cygwin with MinGW in
the same session" part of my advice again.
next prev parent reply other threads:[~2015-03-06 10:08 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 16:34 bug#19989: 25.0.50; Build instructions on Windows Ilya Zakharevich
2015-03-03 17:00 ` Eli Zaretskii
2015-03-03 17:21 ` Eli Zaretskii
2015-03-03 20:30 ` Ilya Zakharevich
2015-03-04 3:42 ` Eli Zaretskii
2015-03-05 21:18 ` Ilya Zakharevich
2015-03-06 8:29 ` Eli Zaretskii
2015-03-06 9:21 ` martin rudalics
2015-03-06 9:59 ` Ilya Zakharevich
2015-03-06 11:16 ` Eli Zaretskii
2015-03-07 1:44 ` Ilya Zakharevich
2015-03-07 9:11 ` Eli Zaretskii
2015-03-08 6:22 ` Ilya Zakharevich
2015-08-15 8:03 ` Eli Zaretskii
2015-08-15 11:22 ` Dani Moncayo
2015-08-15 11:38 ` Dani Moncayo
2015-08-15 12:10 ` Eli Zaretskii
2015-08-15 12:09 ` Eli Zaretskii
2015-08-15 12:24 ` Dani Moncayo
2015-08-15 12:26 ` Eli Zaretskii
2015-08-15 13:39 ` Dani Moncayo
2015-03-06 10:28 ` Eli Zaretskii
2015-03-06 14:13 ` Óscar Fuentes
2015-03-06 14:14 ` Óscar Fuentes
2015-03-06 14:40 ` Eli Zaretskii
2015-03-07 1:47 ` Ilya Zakharevich
2015-03-07 2:04 ` Óscar Fuentes
2015-03-07 9:19 ` Eli Zaretskii
2015-03-06 18:53 ` martin rudalics
2015-03-06 19:27 ` Eli Zaretskii
2015-03-07 9:40 ` martin rudalics
2015-03-07 10:04 ` Eli Zaretskii
2015-03-07 10:28 ` martin rudalics
2015-03-08 6:07 ` Ilya Zakharevich
2015-03-08 10:04 ` martin rudalics
2015-03-08 16:07 ` Ilya Zakharevich
2015-03-06 9:46 ` Ilya Zakharevich
2015-03-06 10:33 ` Eli Zaretskii
2015-03-07 1:37 ` Ilya Zakharevich
2015-03-06 10:08 ` Eli Zaretskii [this message]
2015-03-07 1:35 ` Ilya Zakharevich
2015-03-07 9:04 ` Eli Zaretskii
2015-03-08 6:14 ` Ilya Zakharevich
2015-03-08 15:46 ` Eli Zaretskii
2015-03-08 16:04 ` Ilya Zakharevich
2015-03-08 16:59 ` Eli Zaretskii
2015-03-03 21:15 ` Ilya Zakharevich
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=83h9tyo2v3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19989@debbugs.gnu.org \
--cc=ilya@math.berkeley.edu \
/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).