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

[Vincent Belaïche]

Hello,

> Date: Sun, 7 Oct 2012 16:18:24 +0200
> From: address@hidden
> Subject: Re: [cedet-semantic] Latest CEDET on BZR does not compile with emacs 24.1
> To: address@hidden
> CC: address@hidden; address@hidden; address@hidden
>
> > From: Vincent Belaïche <address@hidden>
> > CC: "address@hidden"
> > <address@hidden>, "address@hidden"
> > <address@hidden>, emacs-devel <address@hidden>
> > Date: Sun, 7 Oct 2012 13:49:19 +0200
> >
> > Here is what I get with
> >
> > mingw32-make.exe bootstrap MAKE=mingw32-make.exe
> >
> > , in a cmd.exe console, but with still MSYS in my path (for rm and such likes):
>
> Keeping MSYS on PATH is a mistake, see below.
>
> > 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
> >
> >
> >
> > For some reason -I ../nt/inc is dropped, well I could just add --cflags -I --cflags ../nt/inc the call of configure.bat.
>
> It's MSYS again, no doubt. Remove MSYS from PATH, and use non-MSYS rm
> and cp.
>
>

I just did that, I installed gnuwin32 into c:/msys/1.0/gnuwin32 (well it may seem a stange location, but I have mingw32 also under msys/1.0, so why not), and I am still getting this:

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

Based on your feedback that making EMACS an MSYS application would be ok only if one would not mind a second emacs just to byte compile a few file, and that GNUWin32's rm & cp are preferable to MSYS's ones, I am now realizing that I was in complete misconception about what MSYS is. I thought that MSYS applications could behave like native Win32 applications when launched outside MSYS. But, best is to quote what MSYS's itself says c.f. http://www.mingw.org/wiki/MSYS

Building for MSYS

To build an application for MSYS (as opposed to using MSYS), users will need to install the MSYS Toolchain. It contains headers and libraries for MSYS along with a patched version of GCC and Binutils. See HOWTO Create an MSYS Build Environment.

It should never be treated as a targeted platform. It is meant only as a means to update the MSYS components or the MSYS runtime DLL itself. Resulting programs will only run under MSYS. 

Actually my misconception stems from this I used MSYS applications quite often outside MSYS and everything worked quite well...

Anyway, thank you very much for your patience.

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?...

VBR,

    Vincent.

PS: for completeness, I attached a tarzip with the complete compile.log and the batch script

compile.tgz
Description: GNU Zip compressed data