From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Cc: Christoph <cschol2112@googlemail.com>
Subject: Re: Compiling Emacs 23.1.92 on Windows fails
Date: Tue, 23 Feb 2010 12:38:35 -0500 [thread overview]
Message-ID: <jwvsk8ram4j.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4B80B4B3.3070609@gmail.com> (Christoph's message of "Sat, 20 Feb 2010 21:21:07 -0700")
> Yes, that turned out to be the problem.
> Using mingw32-make instead of cygwin's make worked and built successfully.
Thanks. Eli, would it be possible to detect the use of cygwin's make
and output a warning in that case?
Stefan
> On 2/20/2010 9:17 PM, Eli Zaretskii wrote:
>>> Date: Sat, 20 Feb 2010 15:46:37 -0700
>>> From: Christoph<cschol2112@googlemail.com>
>>>
>>> I have been trying to compile Emacs Pretest 23.1.92 on Windows 7
>>> (cygwin, MinGW, GnuWin32) but haven't had any luck.
>>>
>>> I run
>>>
>>> configure.bat --no-debug --with-gcc --without-png -cflags
>>> -IC:\Progra~2\GnuWin32\include
>>>
>>> then
>>>
>>> make bootstrap
>>>
>> If you are building the pretest, you don't need to bootstrap, just
>> type "make" after the configure step.
>>
>> If that doesn't help, I suspect that your combination of Cygwin and
>> MinGW tools does not work to build the native port of Emacs (see
>> nt/INSTALL for some combinations that are known to work). E.g., it
>> looks like your Make is a Cygwin port, which is known to fail. It is
>> best to use only MinGW tools for the build.
>>
next prev parent reply other threads:[~2010-02-23 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 22:46 Compiling Emacs 23.1.92 on Windows fails Christoph
2010-02-21 4:17 ` Eli Zaretskii
[not found] ` <4B80B4B3.3070609@gmail.com>
2010-02-23 17:38 ` Stefan Monnier [this message]
2010-02-23 18:27 ` Eli Zaretskii
2010-02-23 19:36 ` Óscar Fuentes
2010-02-24 14:56 ` Sean Sieger
2010-02-24 15:16 ` Sean Sieger
2010-02-24 18:37 ` Eli Zaretskii
2010-02-25 2:15 ` Sean Sieger
2010-02-25 2:55 ` Christoph
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=jwvsk8ram4j.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cschol2112@googlemail.com \
--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.