unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vincent Belaiche <vincent.b.1@hotmail.fr>
Cc: emacs-devel@gnu.org
Subject: Re: Problem building emacs from CVS under MSWindow due to CR/LF and	addsection
Date: Fri, 10 Oct 2008 09:58:01 +0200	[thread overview]
Message-ID: <uwsggj306.fsf@gnu.org> (raw)
In-Reply-To: <uej2pm24f.fsf@gmail.com>

> Date: Fri, 10 Oct 2008 07:48:49 +0200
> From: Vincent Belaiche <vincent.b.1@hotmail.fr>
> 
> Sorry if this problem has been already submitted (actually I could not find
> the bug search for emacs under savannah to check this).
> 
> I have tried to build the latest CVS version of Emacs, this morning under MSW.
> 
> After configuring with configure.bat under cmd.exe, I launched `make
> bootstrap' from the MSYS bash shell.
> 
> I got the following problem
> 
> ---------------
> /c/Programme/GNU/emacs-install/emacs/nt>make bootstrap
> [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
> ', needed by `addsection'.  Stop.
> ---------------
> 
> 
> I edited the makefile under emacs, and I realized that there where plenty of
> ^M charaters which I all removed.
> 
> Thene the make could go a bit further. So I can imagine that the 1st problem I
> met was due to addsection not understanding the CR characters.

No, the problem is because the port of Make you were using does not
grok well the makefile with mixed NL and CR/LF line endings.

I understand that you were using the MSYS shell and Make ports for
building Emacs.  The file nt/INSTALL does not list those as supported
build environments, and about MSYS it says this:

  In addition, using 4NT as your shell is known to fail the build process,
  at least for 4NT version 3.01.  Use CMD.EXE, the default Windows shell,
  instead. MSYS sh.exe also appears to cause various problems. If you have
  MSYS installed, try "make SHELL=cmd.exe" to force the use of cmd.exe
  instead of sh.exe.

In general, a native Windows port of Make (available from the MinGW
site), not the MSYS Make, and stock Windows shell cmd.exe is all you
should need for a successful build.




  reply	other threads:[~2008-10-10  7:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10  5:48 Problem building emacs from CVS under MSWindow due to CR/LF and addsection Vincent Belaiche
2008-10-10  7:58 ` Eli Zaretskii [this message]
2008-10-10  8:13   ` Juanma Barranquero
2008-10-10  9:00     ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2008-10-12 19:09 Vincent Belaïche
2008-10-12 20:11 ` Eli Zaretskii
2008-10-12 22:21 ` Juanma Barranquero
2008-10-14  5:01 Vincent Belaïche
2008-10-19 19:13 Vincent Belaïche
2008-10-20 14:55 ` Eli Zaretskii
2008-10-20 18:33 Vincent Belaïche
2008-10-20 23:50 ` 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=uwsggj306.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=vincent.b.1@hotmail.fr \
    /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).