emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Anyone building Emacs trunk with MinGW w64 (32 bits)


From: Eli Zaretskii
Subject: Re: Anyone building Emacs trunk with MinGW w64 (32 bits)
Date: Wed, 27 Mar 2013 09:24:53 +0200

> From: Óscar Fuentes <address@hidden>
> Date: Tue, 26 Mar 2013 23:30:55 +0100
> 
> Óscar Fuentes <address@hidden> writes:
> 
> > Eli Zaretskii <address@hidden> writes:
> >
> >> Then I guess we need to use _W64 explicitly, see revision 112147.
> >
> > Now emacs.exe is created. Bootstrap in progress.
> 
> There is one minor issue left:
> 
> gcc -I. -c -gdwarf-2 -g3  -mtune=pentium4 -O2    
> -isystemc:/apps/GnuWin32/includ
> e  -o oo-spd/i386/addpm.o addpm.c
> In file included from addpm.c:46:0:
> c:\apps\msys\1.0\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.2/../../../../i686-w6
> 4-mingw32/include/shlobj.h:17:2: error: #error _WIN32_IE setting conflicts
> In file included from 
> c:\apps\msys\1.0\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7
> .2/../../../../i686-w64-mingw32/include/shlobj.h:88:0,
>                  from addpm.c:46:
> c:\apps\msys\1.0\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.2/../../../../i686-w6
> 4-mingw32/include/commctrl.h:17:2: error: #error _WIN32_IE setting conflicts
> In file included from 
> c:\apps\msys\1.0\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7
> .2/../../../../i686-w64-mingw32/include/shlobj.h:91:0,
>                  from addpm.c:46:
> c:\apps\msys\1.0\mingw\bin\../lib/gcc/i686-w64-mingw32/4.7.2/../../../../i686-w6
> 4-mingw32/include/shlguid.h:16:2: error: #error _WIN32_IE setting conflicts
> mingw32-make[1]: *** [oo-spd/i386/addpm.o] Error 1
> mingw32-make[1]: Leaving directory `D:/dev/emacs/emacs/nt'
> 
> 
> As in a previous case, _W64 is checked for definition before _mingw.h is
> (directly or indirectly) #included:
> 
> #ifndef _W64
> #define _WIN32_IE 0x400
> #endif

Right.  Should be fixed now.

Are there any warnings left during MinGW64 compilation?  If so, please
post them.

Also, please try the --no-opt build, it uses slightly more strict
compiler switches, and might trigger warnings the optimized build
doesn't.

Thanks.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]