From: Harald Maier <harald@maierh.de>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 21.3.50 on cygwin bootstrap failed.
Date: Thu, 12 Feb 2004 19:05:29 +0100 [thread overview]
Message-ID: <m3ekt0b2c6.fsf@ate.maierh> (raw)
In-Reply-To: <87hdxwkyet.fsf@offby1.atm01.sea.blarg.net> (Eric Hanchrow's message of "Thu, 12 Feb 2004 09:20:10 -0800")
Eric Hanchrow <offby1@blarg.net> writes:
> "Steven Wu" <wus@qwest.net> writes:
> > I took the CVS src of Emacs 21.3.50 to cygwin and did make
> > bootstrap.
> ...
>
> "Harald Maier" <harald@maierh.de> responds:
> I assume you need the mingw-make 3.79.1.
>
> I'd like to understand this better -- Harald says that one needs the
> MinGW version of `make' to build Emacs under Cygwin. But I am not
> sure that's completely correct. My understanding is that
>
> * the Emacs source tree is capable of building two *different* flavors
> of Emacs -- 1) the so-called "Win32" version (which does not require
> the Cygwin DLLs); and 2) the pure Cygwin version (which of course
> does require the Cygwin DLLs).
>
> * To build the Win32 version, you first cd to the `nt' directory. You
> then have a choice of software with which to do the build: 1)
> Microsoft Visual Studio 6; and 2) the MinGW versions of gcc, make,
> etc., *plus* `cp', `rm', and a few other Unix-style programs. In
> particular, using Cygwin make doesn't work, nor does using the
> Cygwin version of gcc.
>
> * To build the Cygwin version, you do not cd into `nt'; instead you
> simply do `configure && make bootstrap'. However, this always fails
> for me; I assume that the failures are simple mistakes in the Emacs
> source, which will get fixed eventually. I don't believe the
> failures are due to Emacs never having been ported to Cygwin;
> because some files refer to Cygwin (`configure.in', for example). I
> also assume that one does *not* use the MinGW tools when building
> the Cygwin version.
>
> So have I understood everything correctly?
>
> Implicit in my question is a criticism of the file nt/INSTALL; that
> file has cleared up my confusion, and seems out of date. I'd be
> delighted to update it if I only knew the facts.
I think you are right. From Steven's first statement it was not clear
to me that he wants to build a Cygwin Emacs. The second statement
clarified that.
Harald
next prev parent reply other threads:[~2004-02-12 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 8:09 Emacs 21.3.50 on cygwin bootstrap failed Steven Wu
2004-02-12 8:30 ` Harald Maier
2004-02-12 16:08 ` Steven Wu
2004-02-12 17:20 ` Eric Hanchrow
2004-02-12 18:05 ` Harald Maier [this message]
2004-02-12 18:20 ` Jason Rumney
2004-02-13 6:51 ` Harald Maier
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=m3ekt0b2c6.fsf@ate.maierh \
--to=harald@maierh.de \
--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).