Edward Diener <eldlistmaili...@tropicsoft.com> writes: > This is my first time using MSYS2 and, as I understand it, I am running > a Linux-like shell. Within MSYS2 I use a shell command file which > invokes the traditional "configure/make/make install" sequence using the > mingw-64/gcc implementation installed from within MSYS2. This sequence > is the recommended build for the particular library I am building. But > if the mingw-64/gcc implementation in MSYS2 does not understand the > MSYS2 environment it seems that I am using the wrong compiler. Am I > supposed to be installing a Linux gcc implementation instead in MSYS2 ? > Or is my case just an anomaly of using mingw-64/gcc with MSYS2 ?
Please show the exact steps for replicating the problem, including the method you use to start the MSYS2 shell. On the shell you use for the build, if you type the command which gcc.exe what's the output? Configure scripts are usually made of standardized, off-the-shelf components and should detect that you are using the MinGW-w64 toolset and behave in accordance, but the part that puts absolute file paths on the generated __pch.h header possibly is project-specific and might be problematic unless it was written with portability in mind. Does the build work on the classic MSYS environment? Are there reports of it working on Windows at all? ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Msys2-users mailing list Msys2-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/msys2-users
