[ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 868 bytes --]

The mingw-w64 cross compilers have been updated:

* mingw64-i686-binutils-2.28.1.12c1f20d
* mingw64-i686-gcc-6.3.0-1
* mingw64-x86_64-binutils-2.28.1.12c1f20d
* mingw64-x86_64-gcc-6.3.0-1

These versions should be considered testing quality.
Note that ADA/GNAT has been disabled in this release.

              *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com <at> cygwin.com

If you need more information on unsubscribing, start reading here:

http://sourceware.org/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Steven Penny]

On Sun, 20 Aug 2017 14:16:07, JonY wrote:
> The mingw-w64 cross compilers have been updated:
> 
> * mingw64-i686-binutils-2.28.1.12c1f20d
> * mingw64-i686-gcc-6.3.0-1
> * mingw64-x86_64-binutils-2.28.1.12c1f20d
> * mingw64-x86_64-gcc-6.3.0-1
> 
> These versions should be considered testing quality.

Looks good, much thanks. I tested with these projects:

- http://github.com/stedolan/jq
- http://github.com/FFmpeg/FFmpeg
- http://git.videolan.org?p=x264.git

Question - is mingw64-x86_64-gcc-g++ still coming? I have come C++ projects I
could test it with. Also it might resolve this:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=66145


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Steven Penny]

On Sun, 20 Aug 2017 18:57:24, Steven Penny wrote:
> Question - is mingw64-x86_64-gcc-g++ still coming? I have come C++ projects I
> could test it with.

Correcting myself; looks like the Aug 20 update includes C and C++:

http://cygwin.mirror.constant.com/x86_64/release/mingw64-x86_64-gcc


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Steven Penny]

On Sun, 20 Aug 2017 19:45:30, Steven Penny wrote:
> On Sun, 20 Aug 2017 18:57:24, Steven Penny wrote:
> > Question - is mingw64-x86_64-gcc-g++ still coming? I have come C++ projects I
> > could test it with.
> 
> Correcting myself; looks like the Aug 20 update includes C and C++:
> 
> http://cygwin.mirror.constant.com/x86_64/release/mingw64-x86_64-gcc

I am getting an error with the new C++ compiler - it could be a problem with the
project I am compiling, but it seems more like a compiler issue. Here is the
project:

http://github.com/Martchus/tagparser

and here is my build script:

http://github.com/svnpenn/glade/tree/master/tagparser

and here is the error:

[  7%] Building CXX object CMakeFiles/tagparser_static.dir/mp4/mp4tagfield.cpp.o
In file included from
/usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/ext/string_conversions.h:41:0,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/bits/basic_string.h:5402,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/string:52,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/stdexcept:39,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/array:39,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/tuple:39,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/functional:55,
from /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++utilities/chrono/timespan.h:7,
from /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++utilities/chrono/datetime.h:4,
from /var/cache/glade/tagparser/notification.h:6,
from /var/cache/glade/tagparser/statusprovider.h:4,
from /var/cache/glade/tagparser/abstracttrack.h:4,
from /var/cache/glade/tagparser/mp4/mp4track.h:4,
from /var/cache/glade/tagparser/mp4/mp4atom.cpp:1:
/usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/cstdlib:75:25: fatal error:
stdlib.h: No such file or directory
 #include_next <stdlib.h>


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 1414 bytes --]

On 08/22/2017 02:21 AM, Steven Penny wrote:

> [  7%] Building CXX object
> CMakeFiles/tagparser_static.dir/mp4/mp4tagfield.cpp.o
> In file included from
> /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/ext/string_conversions.h:41:0,
> 
> from
> /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/bits/basic_string.h:5402,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/string:52,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/stdexcept:39,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/array:39,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/tuple:39,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/functional:55,
> from
> /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++utilities/chrono/timespan.h:7,
> 
> from
> /usr/x86_64-w64-mingw32/sys-root/mingw/include/c++utilities/chrono/datetime.h:4,
> 
> from /var/cache/glade/tagparser/notification.h:6,
> from /var/cache/glade/tagparser/statusprovider.h:4,
> from /var/cache/glade/tagparser/abstracttrack.h:4,
> from /var/cache/glade/tagparser/mp4/mp4track.h:4,
> from /var/cache/glade/tagparser/mp4/mp4atom.cpp:1:
> /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/cstdlib:75:25: fatal
> error:
> stdlib.h: No such file or directory
> #include_next <stdlib.h>
> 

Seems to be working for me on a minimalist test case. Can you show your
command line and run g++ with -v?



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Steven Penny]

On Tue, 22 Aug 2017 12:47:08, JonY wrote:
> On 08/22/2017 02:21 AM, Steven Penny wrote:
> > stdlib.h: No such file or directory
> > #include_next <stdlib.h>
> >=20
> 
> Seems to be working for me on a minimalist test case. Can you show your
> command line and run g++ with -v?

http://cygwin.com/ml/cygwin/2017-08/msg00193.html

Looks like a Cmake error rather than GCC - thought you might like to know. Cmake
is inserting "-isystem" instead of "-I":

http://github.com/Martchus/tageditor/issues/22#issuecomment-330698400

Side note, our Cmake is now over a year old - but I will post that in separate
thread - thanks


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Steven Penny]

On Tue, 19 Sep 2017 16:14:32, Steven Penny wrote:
> Looks like a Cmake error rather than GCC - thought you might like to know.
> Cmake is inserting "-isystem" instead of "-I":

Looks like I spoke too soon - I think it is a GCC error. Using this file:

$ cat alfa.cpp
#include <cstdio>
#include <functional>
int main() {
  puts("hello world");
}

5.4.0 compiles without issue:

$ x86_64-w64-mingw32-g++ --version
x86_64-w64-mingw32-g++ (GCC) 5.4.0

$ x86_64-w64-mingw32-g++ \
> -I /usr/x86_64-w64-mingw32/sys-root/mingw/include alfa.cpp

$ x86_64-w64-mingw32-g++ \
> -isystem /usr/x86_64-w64-mingw32/sys-root/mingw/include alfa.cpp

However 6.3.0 only works in certain cases:

$ x86_64-w64-mingw32-g++ \
> -I /usr/x86_64-w64-mingw32/sys-root/mingw/include alfa.cpp

$ x86_64-w64-mingw32-g++ \
> -isystem /usr/x86_64-w64-mingw32/sys-root/mingw/include alfa.cpp
In file included from
/usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/ext/string_conversions.h:41:0,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/bits/basic_string.h:5402,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/string:52,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/stdexcept:39,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/array:39,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/tuple:39,
from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/functional:55,
from alfa.cpp:2:
/usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/cstdlib:75:25: fatal error:
  stdlib.h: No such file or directory
#include_next <stdlib.h>

Now really "-I" and "-isystem" are not really needed for this example, because
that directory gets pulled in already - but it should work even with them
included. Also it is somewhat important that it do work even with the redundant
options included, because Cmake often dumps those options in with GCC commands.


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 1510 bytes --]

On 09/21/2017 12:10 AM, Steven Penny wrote:
> 
> $ x86_64-w64-mingw32-g++ \
>> -isystem /usr/x86_64-w64-mingw32/sys-root/mingw/include alfa.cpp
> In file included from
> /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/ext/string_conversions.h:41:0,
> 
> from
> /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/bits/basic_string.h:5402,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/string:52,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/stdexcept:39,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/array:39,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/tuple:39,
> from /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/functional:55,
> from alfa.cpp:2:
> /usr/lib/gcc/x86_64-w64-mingw32/6.3.0/include/c++/cstdlib:75:25: fatal
> error:
>  stdlib.h: No such file or directory
> #include_next <stdlib.h>
> 
> Now really "-I" and "-isystem" are not really needed for this example,
> because
> that directory gets pulled in already - but it should work even with them
> included. Also it is somewhat important that it do work even with the
> redundant
> options included, because Cmake often dumps those options in with GCC
> commands.
> 

I don't really work with cmake, but what it looks like, but it probably
makes gcc look in the mingw include dir first and then gcc's, breaking
gcc's headers.

Unfortunately, I don't have any good ideas besides hacking cmake to
remove the -isystem calls, or contacting gcc-help directly.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Steven Penny]

On Sun, 24 Sep 2017 00:48:20, JonY wrote:
> I don't really work with cmake, but what it looks like, but it probably
> makes gcc look in the mingw include dir first and then gcc's, breaking
> gcc's headers.
> 
> Unfortunately, I don't have any good ideas besides hacking cmake to
> remove the -isystem calls, or contacting gcc-help directly.

Workaround below:

IDR=/usr/x86_64-w64-mingw32/sys-root/mingw/include
cmake -DCMAKE_CXX_IMPLICIT_INCLUDE_DIRECTORIES="$IDR"

http://github.com/svnpenn/glade/blob/f90c642/tagparser/install.sh#L7


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Steven Penny]

On Sun, 24 Sep 2017 00:48:20, JonY wrote:
> I don't really work with cmake, but what it looks like, but it probably
> makes gcc look in the mingw include dir first and then gcc's, breaking
> gcc's headers.
> 
> Unfortunately, I don't have any good ideas besides hacking cmake to
> remove the -isystem calls, or contacting gcc-help directly.

Here is another problem:

$ cat z.cpp
#include <iostream>
main() {
  std::cout << "cout test\n";
}

$ x86_64-w64-mingw32-g++ -static -o z z.cpp

$ ./z
Segmentation fault


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 777 bytes --]

On 09/25/2017 01:53 AM, Steven Penny wrote:
> On Sun, 24 Sep 2017 00:48:20, JonY wrote:
>> I don't really work with cmake, but what it looks like, but it probably
>> makes gcc look in the mingw include dir first and then gcc's, breaking
>> gcc's headers.
>>
>> Unfortunately, I don't have any good ideas besides hacking cmake to
>> remove the -isystem calls, or contacting gcc-help directly.
> 
> Here is another problem:
> 
> $ cat z.cpp
> #include <iostream>
> main() {
>  std::cout << "cout test\n";
> }
> 
> $ x86_64-w64-mingw32-g++ -static -o z z.cpp
> 
> $ ./z
> Segmentation fault

You can actually use Cygwin gdb to debug and see what went wrong,
assuming the debug symbols are around.

Sorry if I'm not much help, kind of busy these days.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Steven Penny]

On Mon, 25 Sep 2017 14:17:28, JonY wrote:
> You can actually use Cygwin gdb to debug and see what went wrong,
> assuming the debug symbols are around.
> 
> Sorry if I'm not much help, kind of busy these days.

New command:

x86_64-w64-mingw32-g++ -g -static -o z z.cpp

Output:

(gdb) run
Starting program: /tmp/z 
[New Thread 5956.0xfe4]
Program received signal SIGSEGV, Segmentation fault.
std::ostream::sentry::sentry (this=this@entry=0x22fd90, __os=...)
  at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
  ostream.tcc:51
51 /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
  ostream.tcc: No such file or directory.
(gdb) backtrace
#0  std::ostream::sentry::sentry (this=this@entry=0x22fd90, __os=...)
    at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
    mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
    ostream.tcc:51
#1  0x000000000049ece9 in std::__ostream_insert<char, std::char_traits<char> >
  (__out=..., 
  __s=__s@entry=0x4ab031 <std::piecewise_construct+1> "cout test\n", __n=10)
  at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
  ostream_insert.h:82
#2  0x00000000004a3547 in std::operator<< <std::char_traits<char> > (
  __out=..., __s=0x4ab031 <std::piecewise_construct+1> "cout test\n")
  at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/std/
  ostream:561
#3  0x00000000004015e0 in main () at z.cpp:3


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 1961 bytes --]

On 09/25/2017 06:33 PM, Steven Penny wrote:
> On Mon, 25 Sep 2017 14:17:28, JonY wrote:
>> You can actually use Cygwin gdb to debug and see what went wrong,
>> assuming the debug symbols are around.
>>
>> Sorry if I'm not much help, kind of busy these days.
> 
> New command:
> 
> x86_64-w64-mingw32-g++ -g -static -o z z.cpp
> 
> Output:
> 
> (gdb) run
> Starting program: /tmp/z [New Thread 5956.0xfe4]
> Program received signal SIGSEGV, Segmentation fault.
> std::ostream::sentry::sentry (this=this@entry=0x22fd90, __os=...)
>  at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
>  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
>  ostream.tcc:51
> 51 /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
>  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
>  ostream.tcc: No such file or directory.
> (gdb) backtrace
> #0  std::ostream::sentry::sentry (this=this@entry=0x22fd90, __os=...)
>    at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
>   
> mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
>    ostream.tcc:51
> #1  0x000000000049ece9 in std::__ostream_insert<char,
> std::char_traits<char> >
>  (__out=...,  __s=__s@entry=0x4ab031 <std::piecewise_construct+1> "cout
> test\n", __n=10)
>  at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
>  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/bits/
>  ostream_insert.h:82
> #2  0x00000000004a3547 in std::operator<< <std::char_traits<char> > (
>  __out=..., __s=0x4ab031 <std::piecewise_construct+1> "cout test\n")
>  at /cygdrive/i/szsz/tmpp/cygwin64/mingw64-x86_64/
>  mingw64-x86_64-gcc-6.3.0-1.x86_64/src/gcc-6.3.0/libstdc++-v3/include/std/
>  ostream:561
> #3  0x00000000004015e0 in main () at z.cpp:3
> 

Looks like the ostream is not properly initialized, all the C++
constructors involved makes it even more messy to debug.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Steven Penny]

On Wed, 27 Sep 2017 23:15:45, JonY wrote:
> Looks like the ostream is not properly initialized, all the C++
> constructors involved makes it even more messy to debug.

http://cygwin.com/ml/cygwin/2017-09/msg00289.html


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Hans-Bernhard Bröker]

Am 25.09.2017 um 03:53 schrieb Steven Penny:
> On Sun, 24 Sep 2017 00:48:20, JonY wrote:
>> I don't really work with cmake, but what it looks like, but it probably
>> makes gcc look in the mingw include dir first and then gcc's, breaking
>> gcc's headers.

Correct thus far.  -isystem is really not a compiler option that CMake 
should be injecting on its own recognizance.  It's for specs files, 
compiler/libc implementation control and such.  It will almost certainly 
break, among other things, any non-trivial use of #include_next.

> Here is another problem:
> 
> $ cat z.cpp
> #include <iostream>
> main() {
>   std::cout << "cout test\n";
> }
> 
> $ x86_64-w64-mingw32-g++ -static -o z z.cpp
> 
> $ ./z
> Segmentation fault

Does not reproduce here.


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Steven Penny]

On Mon, 25 Sep 2017 18:43:27, =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= wrote:
> > Here is another problem:
> > 
> > $ cat z.cpp
> > #include <iostream>
> > main() {
> >   std::cout << "cout test\n";
> > }
> > 
> > $ x86_64-w64-mingw32-g++ -static -o z z.cpp
> > 
> > $ ./z
> > Segmentation fault
> 
> Does not reproduce here.

Scared me for a second - however upon trying this again with a pristine virtual
machine - the error persists

perhap you are using old versions - to repro - you need to be using:

- mingw64-x86_64-binutils 2.28.1
- mingw64-x86_64-gcc-core 6.3.0
- mingw64-x86_64-gcc-g++ 6.3.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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Hans-Bernhard Bröker]

Am 25.09.2017 um 20:44 schrieb Steven Penny:

> perhap you are using old versions 

Not exactly.  I'm using the current versions: 2.25.0.1, 5.4.0 
respectively --- you're using not old enough, a.k.a. still "Test"ing 
versions ;-)


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Andrey Repin]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 688 bytes --]

Greetings, Hans-Bernhard Bröker!

> Am 25.09.2017 um 20:44 schrieb Steven Penny:

>> perhap you are using old versions 

> Not exactly.  I'm using the current versions: 2.25.0.1, 5.4.0 
> respectively --- you're using not old enough, a.k.a. still "Test"ing 
> versions ;-)

Do note that this thread is exactly about test versions.


-- 
With best regards,
Andrey Repin
Wednesday, September 27, 2017 07:30:35

Sorry for my terrible english...\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[Steven Penny]

On Sun, 20 Aug 2017 14:16:07, JonY wrote:
> The mingw-w64 cross compilers have been updated:
> 
> * mingw64-i686-binutils-2.28.1.12c1f20d
> * mingw64-i686-gcc-6.3.0-1
> * mingw64-x86_64-binutils-2.28.1.12c1f20d
> * mingw64-x86_64-gcc-6.3.0-1

http://cygwin.com/ml/cygwin/2017-08/msg00182.html

Can mingw64-{x86_64,i686}-gcc move to Current? These were released about 2
months ago, and it seems the only issue was with binutils, which has already
been fixed and moved to current. Please and thank you.


--
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

Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64} binutils, gcc (Test)

[JonY]

[-- Attachment #1.1: Type: text/plain, Size: 637 bytes --]

On 10/17/2017 11:47 AM, Steven Penny wrote:
> On Sun, 20 Aug 2017 14:16:07, JonY wrote:
>> The mingw-w64 cross compilers have been updated:
>>
>> * mingw64-i686-binutils-2.28.1.12c1f20d
>> * mingw64-i686-gcc-6.3.0-1
>> * mingw64-x86_64-binutils-2.28.1.12c1f20d
>> * mingw64-x86_64-gcc-6.3.0-1
> 
> http://cygwin.com/ml/cygwin/2017-08/msg00182.html
> 
> Can mingw64-{x86_64,i686}-gcc move to Current? These were released about 2
> months ago, and it seems the only issue was with binutils, which has
> already
> been fixed and moved to current. Please and thank you.
> 

Sure, I'll bump it soon, thanks for testing.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 858 bytes --]