Thanks for the reply. I knew I needed to use gcc from the appropriate mingw directory. I wasn't trying to use anything different. As I mentioned and explained, it was mistakenly using cc, there was a hidden bug (failure to export CC) in the shell script that got exposed. "cc" and "gcc" look pretty similar when flying past as the program compiles, I just assumed it was using gcc.
Thanks for clarifying the purpose of the various gcc / cc executables. That helps. Daniel On 11/2/2015 12:49 AM, Alexpux wrote: > >> 2 нояб. 2015 г., в 11:42, Daniel Goldman <[email protected] >> <mailto:[email protected]>> написал(а): >> >> On 11/1/2015 11:03 PM, Greg Jung wrote: >>> msys2 does not install anything in /opt/. >>> But you don't have to choose, >>> because gcc will find >>> the directories it needs. >>> >> >> $ find / -name dos.h >> /mingw32/i686-w64-mingw32/include/dos.h >> /mingw64/x86_64-w64-mingw32/include/dos.h >> /opt/i686-w64-mingw32/include/dos.h >> /opt/x86_64-w64-mingw32/include/dos.h >> >> If msys2 didn't install anything in /opt directory, then who did? :) I >> certainly didn't copy anything there. There seem to be duplicate files >> all over the place. >> >> Nevertheless, you're right, gcc will find the directories. It was >> complaining before, and I was having to set -I flag, because I was >> mistakenly compiling with cc, instead of intended gcc. A shell script >> was setting CC, but mistakenly not exporting. On ubuntu linux, it didn't >> matter, because cc == gcc. But here is did matter. >> >> $ cc hello.c >> hello.c:2:17: fatal error: dos.h: No such file or directory >> #include <dos.h> >> ^ >> compilation terminated. >> $ >> >> Once the shell script was fixed up, exported CC, the makefile saw to use >> gcc instead of cc, it automatically finds the directories. >> >> $ gcc hello.c >> $ >> >> Thanks! > > You MUST use GCC from /mingw{32,64} locations to build native windows > applications. > We have mingw cross-compiler in /opt for our own purposes - for building > MSYS2 runtime. Don’t use it yourself. > > Also GCC from /usr is MSYS-gcc (like cygwin-gcc) and it only needed for > developing msys2 applications. > > Regards, > Alexey. >> >>> On Sun, Nov 1, 2015 at 9:31 PM, Daniel Goldman <[email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected]>> wrote: >>> >>> What's the difference between the following two directories? >>> >>> $ ls /opt/i686-w64-mingw32/include/ | wc >>> 1351 1351 14418 >>> $ ls /mingw32/i686-w64-mingw32/include | wc >>> 1487 1487 16404 >>> >>> Which should I use for compiling a 32 bit windows application? >>> >>> Thanks, >>> Daniel >>> >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Msys2-users mailing list >>> [email protected] >>> <mailto:[email protected]> >>> <mailto:[email protected]> >>> https://lists.sourceforge.net/lists/listinfo/msys2-users >>> >>> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Msys2-users mailing list >> [email protected] >> <mailto:[email protected]> >> https://lists.sourceforge.net/lists/listinfo/msys2-users > ------------------------------------------------------------------------------ _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
