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

2016-07-24 Thread Ricardo Constantino
Recompiling GCC with https://github.com/Alexpux/MINGW-packages/pull/1588/commits/ba282a67e971e045131291fd0f21ef786b82b1b1 seems to fix the issue for me. I don't know enough to be sure this doesn't break anything else. The alternative would be disabling the patch that enables libitm, but I assumed j

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

2016-07-24 Thread lh mouse
It looks normal. I thought it could be caused by linking a 64-bit object file against a 32-bit library. Fortunately, it isn't the case. FWIW, two months ago I sent a pull request about the GCC relocation bug here: https://github.com/Alexpux/MINGW-packages/pull/1444 A few days ago on IRC, alexey m

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

2016-07-24 Thread Ricardo Constantino
Additionally, someone else also got these same errors with a self-compiled GCC 6[1], so it's maybe not specific to MSYS2-compiled GCC but something involving GCC 6 and mingw-w64. [1] https://github.com/lachs0r/mingw-w64-cmake/commit/ac8e62c493d5ebebe61e59d1db39bfb1c08e7888

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

2016-07-24 Thread Ricardo Constantino
On 2016-07-24 16:14, lh mouse wrote: > 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" > $ objdump -f "C:/builds/ab/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/6

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

2016-07-24 Thread lh mouse
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] Relocation errors when linking with static libstdc++ starting with GCC 6 (64-bit only)

2016-07-24 Thread Nakai Yuta
>> Hi >> >> Any short test case to reproduce? >> >> >I've been told specifically that libs that don't use exceptions don't >suffer from this, like x265. >Rubberband does, though. > >``` >(open mingw64-shell) > >export CC=gcc >#MINGW_PREFIX=/mingw64 > >git clone https://github.com/lachs0r/rubberband

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

2016-07-24 Thread Ricardo Constantino
On 24 July 2016 at 13:51, Nakai Yuta wrote: > Hi > > Any short test case to reproduce? > > I've been told specifically that libs that don't use exceptions don't suffer from this, like x265. Rubberband does, though. ``` (open mingw64-shell) export CC=gcc #MINGW_PREFIX=/mingw64 git clone https:/

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

2016-07-24 Thread Nakai Yuta
Hi Any short test case to reproduce? Sent from Outlook 差出人: Ricardo Constantino 送信日時: 2016年7月24日 21:30 宛先: mingw-w64-public@lists.sourceforge.net 件名: [Mingw-w64-public] Relocation errors when linking with static libstdc++ starting with GCC 6 (64-bit only

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

2016-07-24 Thread Ricardo Constantino
Both FFmpeg and mpv when linking with -lstdc++ fail with these exact errors when compiling with x86_64-w64-mingw32 GCC 6.1 There errors are only fixed by not including libs which need libstdc++ or by reverting to GCC 5.4. Haven't tried not using static libstdc++, since I'd prefer not depending