GNU bug report logs - #10665
24.0.93; Building for MS Windows using MinGW encounters a build problem in ../emacs-24.0.93/src/makefile

Previous Next

Full log

Message #14 received at 10665-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: "Gallagher, Kevin" <Kevin.Gallagher <at> boeing.com>
Cc: 10665-done <at> debbugs.gnu.org
Subject: Re: bug#10665: 24.0.93;
	Building for MS Windows using MinGW encounters a build problem
	in	../emacs-24.0.93/src/makefile
Date: Tue, 31 Jan 2012 06:05:03 +0200

> From: "Gallagher, Kevin" <Kevin.Gallagher <at> boeing.com>
> CC: "10665-done <at> debbugs.gnu.org" <10665-done <at> debbugs.gnu.org>
> Date: Mon, 30 Jan 2012 19:12:27 -0600
> 
> Here's the version of MSYS bash that I find to be excellent.
> 
>   GNU bash, version 3.1.17(1)-release (i686-pc-msys)
>   Copyright (C) 2005 Free Software Foundation, Inc.

OK, I will add this.  Thanks.

> As for a command in a rule which does nothing, this works:
> 
>  globals.h: gl-stamp
> 	@echo
> 
> OK, technically it outputs a linefeed to stdout, but that is harmless in this context and requires less overhead than the original. (Both bash and cmd.exe have an echo command and both recognize the "@" syntax at the start of a command.)

It's true that both bash and cmd support @echo, but in cmd just
"@echo" will produce "ECHO is on.", not an empty line.  The trick with
"rem" and the invocation through "cmd /c" are to countermand that,
because we need a Makefile that will work both when Bash is the shell
and when cmd is the shell.

> In the original syntax:
> 
>    globals.h: gl-stamp
>          @cmd /c rem true
> 
> make passes the command line to a sub-shell in which the invocation of cmd creates a second nested sub-shell where the line "rem true" is interpreted as a batch file "remark" command.

"Rem" is not just a batch file command, it is a first-class command in
cmd.  You can type it from the command line, for example.

> Here's some additional information for nt/INSTALL.
> 
> 1. When building on Windows XP, the option "-fno-omit-frame-pointer" must be used.  Otherwise, entering a C-g will cause Emacs to crash.  NOTE:  It turns out that this is not necessary when building on Windows 7.  (I don't have any information about other versions of Windows.)

This is needed only with GCC 4.6.x, see etc/PROBLEMS.

> 2. When building in MSYS bash, the following syntax for invoking the configure script must be used:
> 
>   cmd /c "configure.bat --cflags -fno-omit-frame-pointer"
> 
>       or
> 
>   cmd /c "configure.bat --cflags -IC:/extras/include --cflags -fno-omit-frame-pointer"
> 
> In other words, configure.bat MUST be included within the double quotes.
> 
> 3. Whether building in the bash shell or the cmd.exe shell, when using the MinGW tool set, all -I options passed to configure.bat must use the "drive-letter:" syntax with FORWARD slashes in the path!

This is already mentioned, thanks.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.