From: Eric Hanchrow <offby1@blarg.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: William Xue <william.xue@gmail.com>, emacs-devel@gnu.org
Subject: Re: Help: build emacs in cygwin
Date: Wed, 07 Mar 2007 08:47:51 -0800 [thread overview]
Message-ID: <87wt1tm24o.fsf@offby1.atm01.sea.blarg.net> (raw)
In-Reply-To: <ufy8hn0r6.fsf@gnu.org> (Eli Zaretskii's message of "Wed\, 07 Mar 2007 06\:19\:57 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> I think that's a very bad idea: MinGW and Cygwin are deeply
Eli> incompatible. So please do NOT use the MinGW Make to build
Eli> the Cygwin port of Emacs.
Uh oh. I suggested that only because nt/INSTALL says
(If you are building from CVS, say "make bootstrap" or "nmake
bootstrap" instead, and avoid using Cygwin make.)
The MinGW "make" is the only Free "make" I know of that works to build
emacs on Cygwin, and it's been working without problem for me for
literally years. What's wrong with it, and what would you recommend
in its place?
--
Asking the Iraqi people to assume Saddam's debts
is rather like telling a man who has been shot in the head
that he has to pay for the bullet.
-- James Surowiecki
next prev parent reply other threads:[~2007-03-07 16:47 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 8:01 Help: build emacs in cygwin William Xue
2007-03-06 20:40 ` Eli Zaretskii
2007-03-07 1:27 ` William Xue
2007-03-07 4:24 ` Eli Zaretskii
2007-03-07 8:22 ` William Xue
2007-03-08 4:49 ` William Xue
2007-03-09 14:31 ` Eli Zaretskii
2007-03-09 21:26 ` Richard Stallman
2007-03-10 18:56 ` Eli Zaretskii
2007-03-12 5:26 ` Harald Maier
2007-03-12 22:01 ` Eli Zaretskii
[not found] ` <87ejo2nrf6.fsf@offby1.atm01.sea.blarg.net>
2007-03-07 1:23 ` William Xue
2007-03-07 4:19 ` Eli Zaretskii
2007-03-07 16:47 ` Eric Hanchrow [this message]
2007-03-08 4:13 ` Eli Zaretskii
2007-03-08 6:49 ` Eric Hanchrow
2007-03-09 14:40 ` Eli Zaretskii
2007-03-08 7:01 ` djh
2007-03-09 15:11 ` Eli Zaretskii
2007-03-09 21:26 ` Richard Stallman
2007-03-10 9:38 ` Jan Djärv
2007-03-10 19:04 ` Eli Zaretskii
2007-03-11 4:23 ` Richard Stallman
2007-03-20 7:36 ` Jan Djärv
2007-03-21 0:42 ` Richard Stallman
2007-03-13 0:17 ` djh
2007-03-13 4:22 ` Eli Zaretskii
[not found] ` <20070313145148.3496@henman-np.b-eng.it.to-be.co.jp>
2007-03-13 20:56 ` Eli Zaretskii
2007-03-07 17:25 ` Richard Stallman
2007-03-08 4:14 ` Eli Zaretskii
2007-03-08 21:47 ` Richard Stallman
2007-03-09 14:36 ` Eli Zaretskii
2007-03-09 21:26 ` Richard Stallman
2007-03-10 18:52 ` Eli Zaretskii
2007-03-11 20:00 ` Richard Stallman
2007-03-09 15:34 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2007-03-09 15:24 Help: build emacs in cygwin (fwd) Eli Zaretskii
2007-03-13 13:10 ` Help: build emacs in cygwin Angelo Graziosi
2007-03-13 18:23 ` Harald Maier
2007-03-14 0:52 ` Angelo Graziosi
2007-03-14 1:31 ` djh
2007-03-14 7:41 ` Jason Rumney
2007-02-23 18:15 cygwin succesfull straight build Eli Zaretskii
2007-03-07 13:37 ` Help: build emacs in cygwin Angelo Graziosi
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=87wt1tm24o.fsf@offby1.atm01.sea.blarg.net \
--to=offby1@blarg.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=william.xue@gmail.com \
/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).