Re: [Mingw-w64-public] [Msys2-users] Relocation errors when linking with static libstdc++ starting with GCC 6 (64-bit only)

LRN, the author of the libitm patch of MSYS2 gcc package, suggested disabling it: [22:57:27] LRN, wasn't you the guy who wrote the enable-libitm patch for MSYS2 ? [22:57:36] s/wasn't/weren't/ [22:57:42] that is quite possible [22:58:02] possible ? :S [22:58:07] I don't remember [22:58:13]

Re: [Mingw-w64-public] [Msys2-users] Relocation errors when linking with static libstdc++ starting with GCC 6 (64-bit only)

am not sure. -- Best regards, lh_mouse 2016-07-25 - 发件人：Ricardo Constantino <wiia...@gmail.com> 发送日期：2016-07-25 09:30 收件人：lh mouse 抄送：msys2-users,mingw-w64-public 主题：Re: Re: [Msys2-users] R

Re: [Mingw-w64-public] [Msys2-users] Relocation errors when linking with static libstdc++ starting with GCC 6 (64-bit only)

am not sure. -- Best regards, lh_mouse 2016-07-25 - 发件人：Ricardo Constantino <wiia...@gmail.com> 发送日期：2016-07-25 09:30 收件人：lh mouse 抄送：msys2-users,mingw-w64-public 主题：Re: Re: [Msys2-users] R

Re: [Mingw-w64-public] [Msys2-users] Relocation errors when linking with static libstdc++ starting with GCC 6 (64-bit only)

2016-07-24 - 发件人：Ricardo Constantino <wiia...@gmail.com> 发送日期：2016-07-24 23:19 收件人：lh mouse,msys2-users,mingw-w64-public 抄送： 主题：Re: [Msys2-users] Relocation errors when linking with static libstdc++ starting with GCC 6 (64-bit only) On 2016-07-24 16:14, lh mouse wrote: > Try thi

Re: [Mingw-w64-public] [Msys2-users] Relocation errors when linking with static libstdc++ starting with GCC 6 (64-bit only)

Try this command and reply with its output: objdump -f "C:/builds/ab/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/6.1.0\libstdc++.a" | grep "cow-stdexcept.o" -- Best regards, lh_mouse 2016-07-24

Re: [Mingw-w64-public] g++ throwing compiler out with the bathwater

The only valid syntax to declare a const reference to an std::string is 'std::string const & first' or 'const std::string & first'. Putting the const qualifier elsewhere is an error. Get a C++ book, teach yourself and stop spamming this list. Your questions are not only too basic but also

Re: [Mingw-w64-public] bug in 20160708 x32 x32, STDERR not defined in stdio.h

It is not a bug. The macro for the standard error stream is `stderr` rather than `STDERR`. -- Best regards, lh_mouse 2016-07-16 - 发件人：Jim Michaels

Re: [Mingw-w64-public] Prebuilt GCC binaries 6.1.1 for x86 and x64 with MCF thread model

- 发件人：niXman <i.nix...@autistici.org> 发送日期：2016-07-13 00:34 收件人：mingw-w64-public 抄送： 主题：Re: [Mingw-w64-public] Prebuilt GCC binaries 6.1.1 for x86 and x64 with MCF thread model lh mouse 2016-07-12 19:03: > https://github.com/lhmouse/mcfgthread

Re: [Mingw-w64-public] Prebuilt GCC binaries 6.1.1 for x86 and x64 with MCF thread model

016-07-13 00:01 收件人：mingw-w64-public 抄送： 主题：Re: [Mingw-w64-public] Prebuilt GCC binaries 6.1.1 for x86 and x64 with MCF thread model lh mouse 2016-07-12 18:53: > Hello everyone, Hi, > I have been bootstrapping GCC with MCF thread model for months and I > think it is > time to ma

[Mingw-w64-public] Prebuilt GCC binaries 6.1.1 for x86 and x64 with MCF thread model

Hello everyone, I have been bootstrapping GCC with MCF thread model for months and I think it is time to make it known. Tests and reports are welcome. Packages of prebuilt binaries can be found here: http://96.44.178.21/gcc-mcf/ The part in the back of a file name is the SHA-1 checksum of

Re: [Mingw-w64-public] Confirmation of a potential bug of g++ 6.1 targeting i686 requested

__builtin_memcpy() works fine there without any ICE. ``` E:\Desktop>cat test.cpp auto p = &__builtin_memcpy; E:\Desktop>gcc test.cpp -c E:\Desktop> ``` -- Best regards, lh_mouse 2016-07-05

[Mingw-w64-public] Confirmation of a potential bug of g++ 6.1 targeting i686 requested

Have you guys got g++ 6.1? I am now suffering from an ICE, but I am not sure whether it is a bug of GCC. I am looking forward to your opinions. If this is indeed a GCC bug I will file it soon. ** Note: the function `memcpy` is declared manually to avoid #include'ing any system headers. The

Re: [Mingw-w64-public] Proposal for a C11 header and announcement of mcfgthread, a library that implements efficient C11 and C++11 thread support without using winpthread

Yes. There are two major reasons at the moment: 0. The gthread and c11 thread use global BSTs to translate thread IDs to HANDLEs upon *_join() or *_detach() calls, which would be problematic if mcfgthread is linked statically, since each dynamic library as well as the executable is going to

Re: [Mingw-w64-public] Proposal for a C11 header and announcement of mcfgthread, a library that implements efficient C11 and C++11 thread support without using winpthread

chism of mingw-w64 thread configurations is really great. Regards Carl 2016-06-18 21:10 GMT+02:00 lh mouse <lh_mo...@126.com>: > Hello everyone, > > It is with great honor that I bring you the C11-conforming header for > thread support of mcfgthread, c11thread.h: > http

[Mingw-w64-public] Proposal for a C11 header and announcement of mcfgthread, a library that implements efficient C11 and C++11 thread support without using winpthread

Hello everyone, It is with great honor that I bring you the C11-conforming header for thread support of mcfgthread, c11thread.h: https://github.com/lhmouse/mcfgthread/blob/master/src/env/c11thread.h All headers in the mcfgthread project have been put into the public domain. As JonY suggested a

Re: [Mingw-w64-public] Autotools & git

Lack of a running `configure` script might results in the following output in your user's terminal: (This is partially a joke. So please enjoy.) --- LH_Mouse@LH-PC /e/Desktop/gcc $ autoreconf -i configure.ac:33: error: Please use exactly Autoconf 2.64 instead of 2.69. config/override.m4:12:

Re: [Mingw-w64-public] winpthreads, pthread_setschedparam, and detached threads

Note that in most cases threads other than the one calling `pthread_detach()` can terminate at anytime. After a call `pthread_detach()`, if the thread terminates, its resources are freed automatically, rendering the `pthread_t` no longer valid. It is impossible to tell whether a `pthread_t` is

Re: [Mingw-w64-public] Need a prebuild MinGW-w64 with configuration of "--enable-nls"

Your attachment seemed swallowed. Anyway, if you have a problem about MSYS2 patches or packages you can open an issue or pull request on GitHub. -- Best regards, lh_mouse 2016-05-13 -

Re: [Mingw-w64-public] ignoring missing symbols doesn't seem to work

Usually a static archive (.a file) is created with 'ar' rather than 'g++'. To create an object file (.o file) that can be linked later on, use the following command: ld -r -o I never use gcc/g++ to do that. -- Best regards, lh_mouse 2016-05-11

Re: [Mingw-w64-public] Need a prebuild MinGW-w64 with configuration of "--enable-nls"

显示.后来发现是对vfprintf函数的支持问题,但我没法修复这个问题. 2016-05-10 15:50 GMT+08:00 lh mouse <lh_mo...@126.com>: > You might want to build one yourself. You can find something useful here: > https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-gcc-git > > Generally I wouldn't recom

Re: [Mingw-w64-public] Need a prebuild MinGW-w64 with configuration of "--enable-nls"

You might want to build one yourself. You can find something useful here: https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-gcc-git Generally I wouldn't recommend use of NLS, because it turns out to be hard to get anything useful by feeding a search engine with any non-English