unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: jasonr (Jason Rumney) @  f2s.com
Subject: Re: Newbie: Compiling Emacs 21.2 with MinGW
Date: 02 Sep 2003 21:26:08 +0100	[thread overview]
Message-ID: <uwucrhr8e.fsf@jasonrumney.net> (raw)
In-Reply-To: e808b168.0309020406.ce7c338@posting.google.com

Kai.Grossjohann@gmx.net (Kai Grossjohann) writes:

> I'm trying to compile Emacs 21.2 (it's the most recent tarball I could
> find,
> emacs-21.3.tar.gz seems to be still down) with MinGW.  I have no
> experience
> whatsoever using Windows and MinGW...
> 
> Anyhow, I installed MinGW and MSYS.  I added c:\mingw\bin and
> c:\msys\1.0\bin to %PATH%.  Then I went to the emacs-21.2/nt directory
> and invoked:
> 
>     configure --prefix=c:\programme\emacs-21.2

Windows batch files cannot (easily) understand --option=value, so you
need to use "configure --prefix c:\programme\emacs-21.2". If you are
using sh.exe (I am not sure it works, only cmd.exe and Cygwin
bash.exe have been tested), then you will need to use forward slashes
and include the .bat extension I think.

> It told me to run gmake.  I don't have gmake.  So I ran make instead,
> which gave an error.  Running make again gives the following output:
> 
> E:\src\emacs\emacs-21.2\nt>make
> [Please ignore a syntax error on the next line - it is intentional]
> /bin/sh.exe: -c: line 1: unexpected EOF while looking for matching `"'
> /bin/sh.exe: -c: line 2: syntax error: unexpected end of file

It looks like you are using sh.exe. As I said, this is untested, so
maybe you should try starting from scratch using the native Windows
shell. If that does not work, Cygwin bash should (that is what I use
when building with gcc).

> w32fns.c:13973:1: directives may not be used inside a macro argument
> w32fns.c:13963:16: unterminated argument list invoking macro
> "DEFVAR_LISP"

This is suspicious. Can you look at line 13963 of that file and see
what it says?

> w32fns.c: In function `syms_of_w32fns':
> w32fns.c:13974: `DEFVAR_LISP' undeclared (first use in this function)
> w32fns.c:13974: (Each undeclared identifier is reported only once
> w32fns.c:13974: for each function it appears in.)
> w32fns.c:13974: parse error before string constant
> make[1]: *** [oo-spd/i386/w32fns.o] Error 1
> make[1]: Leaving directory `/e/src/emacs/emacs-21.2/src'
> make: *** [all-other-dirs-gmake] Error 2
> 
> E:\src\emacs\emacs-21.2\nt>
> 
> So, what do I do now?
> 
> Is it fixed in 21.3?

Unlikely. There were no Windows specific fixes in 21.3 that I know
of.

  parent reply	other threads:[~2003-09-02 20:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 12:06 Newbie: Compiling Emacs 21.2 with MinGW Kai Grossjohann
2003-09-02 13:41 ` Matthias Rempe
2003-09-04  9:46   ` Kai Grossjohann
2003-09-02 14:13 ` Peter Lee
2003-09-02 14:37 ` lawrence mitchell
2003-09-02 20:28   ` Jason Rumney
2003-09-02 20:26 ` Jason Rumney [this message]
2003-09-03 13:02   ` Vladimir Grul
2003-09-03 21:11     ` Jason Rumney
2003-09-03  7:19 ` Vladimir Grul
2003-09-03 11:46 ` Eli Zaretskii

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=uwucrhr8e.fsf@jasonrumney.net \
    --to=jasonr@f2s.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.
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).