Re: [cedet-semantic] Latest CEDET on BZR does not compile with emacs 24.1

[Eli Zaretskii <eliz@gnu.org>]

> From: Vincent Belaïche <vincent.b.1@hotmail.fr>
> Date: Sun, 7 Oct 2012 18:37:11 +0200
> Cc: "cedet-semantic@lists.sourceforge.net"
> 	<cedet-semantic@lists.sourceforge.net>,
> 	"deng@randomsample.de" <deng@randomsample.de>,
> 	emacs-devel <emacs-devel@gnu.org>
> 
> rm stamp_BLD
> mingw32-make.exe[1]: Leaving directory `C:/Programme/GNU/installation/emacs-install/emacs/trunk/lib-src'
> mingw32-make.exe   -C ../lib-src make-docfile
> mingw32-make.exe[1]: Entering directory `C:/Programme/GNU/installation/emacs-install/emacs/trunk/lib-src'
> mkdir "oo-spd"
> mkdir "oo-spd/i386"
> echo oo-spd/i386 > stamp_BLD
> gcc -I ../src -I. -c -gdwarf-2 -g3  -mtune=pentium4 -O2    -I C:/Programme/GNU/installation/emacs-install/libXpm-3.5.7/include -I C:/Programme/GNU/installation/emacs-install/libXpm-3.5.7/src  -o oo-spd/i386/make-docfile.o make-docfile.c
> In file included from ../src/config.h:1673:0,
>                  from make-docfile.c:37:
> ../src/conf_post.h:32:27: fatal error: ms-w32.h: No such file or directory
> compilation terminated.
> mingw32-make.exe[1]: *** [oo-spd/i386/make-docfile.o] Error 1
> 
> Id est, for some mysterious reason -I ../nt/inc again disappeared. The batch file that makes this is the following (with some simplification):
> SET PATH=C:\Programme\GNU\installation\emacs-install\libXpm-3.5.7\src;C:\msys\1.0\mingw\bin;C:\msys\1.0\gnuwin32\bin;C:\WINDOWS\system32;C:\WINDOWS
> CALL configure.bat --prefix=C:\Programme\GNU\Emacs --without-jpeg --without-tiff --without-gif --without-png  --distfiles C:\Programme\GNU\installation\emacs-install\libXpm-3.5.7\src --cflags -I --cflags "C:/Programme/GNU/installation/emacs-install/libXpm-3.5.7/include" --cflags -I --cflags "C:/Programme/GNU/installation/emacs-install/libXpm-3.5.7/src"
> mingw32-make.exe bootstrap MAKE=mingw32-make.exe

I have no idea what's going on there.  What version of Emacs is that?
The compilation switches passed to GCC are nowhere near what I'd
expect given the value of LOCAL_FLAGS in lib-src/makefile.w32-in.

> I am now starting to wonder whether all my troubles aren't coming from this that I may have mistakenly some components of my supposedly MingW32 toolchain patched to build for MSYS, rather than to use MSYS. How can one detect that?...

Look inside the .exe with some dependency checker; if you see a
dependency on MSYS-1.0.DLL, it's an MSYS executable.