Hi Steve, 2017/2/14 Tue 4:03:04 UTC+9 Steve Hall wrote: > I've just recently starting seeing this error building on Win x64 with > Cygwin: > > > i686-pc-mingw32-gcc -c -Iproto -DWIN32 -DWINVER=0x0501 -D_WIN32_WINNT=0x0501 > -DHAVE_PATHDEF -DFEAT_HUGE -DHAVE_STDINT_H -DMS_WIN64 - DHAVE_GETTEXT > -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG > -DFEAT_JOB_CHANNEL -DFEAT_GUI_W32 -DFEAT_CLIPBOAR D -DFEAT_MBYTE > -DFEAT_MBYTE_IME -DDYNAMIC_IME -DDYNAMIC_ICONV -pipe -march=x86-64 -Wall -O3 > -fomit-frame-pointer -freg-struct-return -s charset.c -o gobjx86-64/charset.o > charset.c: In function 'vim_str2nr': > charset.c:1915:15: error: '_UI64_MAX' undeclared (first use in this function) > charset.c:1915:15: note: each undeclared identifier is reported only once for > each function it appears in > charset.c:1981:15: error: '_I64_MAX' undeclared (first use in this function) > charset.c:1982:11: error: '_I64_MIN' undeclared (first use in this function) > make: *** [Make_cyg_ming.mak:887: gobjx86-64/charset.o] Error 1 > > > Any hints?
Are you really using i686-pc-mingw32-gcc for x64 build? It is a compiler for x86 build. You should use x86_64-w64-mingw32-gcc for x64 build. Set 'CROSS_COMPILE=x86_64-w64-mingw32-' to use it. Additionally, you don't need to set ARCH=x86-64 manually after v7.4.2034. Normally, ARCH will be automatically detected after that. For 32-bit build, I recommend i686-w64-mingw32-gcc instead of i686-pc-mingw32-gcc. Regards, Ken Takata -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
