On 27. 4. 2015 9:07, Rainer Schuetz wrote: > Hi, > > Apparently doesn’t go true. So I post with files pasted. I cut the cli one > off, because the mail is to long for list server. > > Found it, thanks. Trying first to send the logs as attachments. But the > difference is quite clear: one version checks for compiler-version with -v > (DOS) and the ssh one with -V (which triggers the error).
Looking at the attached logs, I see that both of them call gcc -V with the same
failure and the difference is actually in this command:
i686-w64-mingw32-gcc -march=i686 -mtune=generic -O2 -pipe -D_FORTIFY_SOURCE=2
-D__USE_MINGW_ANSI_STDIO=1 -pipe conftest.c
I have no idea why that would fail in one case and not in the other. Does that
command fail when run from the SSH command line (without going through
configure)? You may have to check the exit code (by running `echo $?` as the
next command).
The contents of conftest.c is in the log, but I'll also paste it here:
/* confdefs.h */
#define PACKAGE_NAME ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define PACKAGE_STRING ""
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
--
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
