On 5. 5. 2015 18:58, Rainer Schuetz wrote: > Hi David, > > sorry for taking some time... > > I can’t fully understand the implications of what you explain, so I just do > what you say in hope it turns up something useful. > > Running the i686-w64......test.c line on the ssh command line returns an > error: > > $ i686-w64-mingw32-gcc -march=i686 -mtune=generic -O2 -pipe > -D_FORTIFY_SOURCE=2 -D__USE_MINGW_ANSI_STDIO=1 -pipe conftest.c > bash: i686-w64-mingw32-gcc: command not found > >> echo $? > > returns 127 > > It is actually not surprising that i686-w64-mingw32-gcc is not found as > /mingw32/bin is not in the path. But I have been doing all the different > builds in the msys shell only (well msys in an s-shell), and the 64-bit one > went through as well... > > Is that of any help?
Sorry, I didn't realize. Please retry with the correct /mingw??/bin directory in PATH, or use an absolute path to gcc (/mingw32/bin/i686-w64-mingw32-gcc). -- David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
