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

I get the same failure here [1], smallest reproducible test case so far, unfortunately, seems to be cross compiling ffmpeg like ffmpeg's configure --arch=x86_64 --target-os=mingw32 --enable-librubberband --enable-gpl then it fails (no msys2 at play at all in this case). [1]

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)

I have compiled ffmpeg with LDFLAGS='-static-libgcc -static-libstdc++' and Stud_PE says ffmpeg.exe doesn't import anything from libitm, nor does it import anything from libstdc++, libgcc, libiconv, etc. I also asked it on #mingw-w64 on OFTC and people said it seemed mere undefined references

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

On 25 July 2016 at 12:18, lh mouse wrote: > I have compiled ffmpeg with LDFLAGS='-static-libgcc -static-libstdc++' and > Stud_PE says ffmpeg.exe doesn't import anything from libitm, nor does it > import > anything from libstdc++, libgcc, libiconv, etc. > > It doesn't, by

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

I have compiled ffmpeg with LDFLAGS='-static-libgcc -static-libstdc++' and Stud_PE says ffmpeg.exe doesn't import anything from libitm, nor does it import anything from libstdc++, libgcc, libiconv, etc. I also asked it on #mingw-w64 on OFTC and people said it seemed mere undefined references

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

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

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

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

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

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)

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

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