On Wed, 27 Sep 2017 14:42:43, =?UTF-8?B?5Y+26Zuo6aOe?= wrote:
This is actually not the same issue at
https://cygwin.com/ml/cygwin/2017-09/msg00236.html
In my case, it is caused by latest binutils 2.28 , when using 2.25
everything is fine (even with gcc-6.4)
Maybe we should hold back upgrading binutils , or maybe it need a more
recent version? There seems to be binutils 2.29.1 now
Actually, it is the same issue:
$ cygcheck -s | grep -e binutils -e gcc
mingw64-x86_64-binutils 2.25.0.1.23f238d-1 OK
mingw64-x86_64-gcc-core 6.3.0-1 OK
mingw64-x86_64-gcc-g++ 6.3.0-1 OK
$ cat z.cpp
#include <iostream>
main() {
std::cout << "cout test\n";
}
$ x86_64-w64-mingw32-g++ -static -o z z.cpp
$ ./z
cout test
So, with both your post and my post, the issue is fixed by not using:
- binutils 2.28.1
- mingw64-x86_64-binutils 2.28.1
- mingw64-i686-binutils 2.28.1
which leaves the last working version:
- binutils 2.25.0
- mingw64-x86_64-binutils 2.25.0
- mingw64-i686-binutils 2.25.0
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
