Re: [Mingw-w64-public] Default _WIN32_WINNT version too low?

On 3 June 2017 at 19:52, Mateusz Mikuła wrote: > 0x0502 is Windows Server 2003 > > If changing default target it should be done properly. Windows Vista is > EOL and it's share is lower than XP so I'd vote for Windows 7. > > > -- Original Message -- > Subject:

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

On 8 February 2017 at 02:55, Liu Hao <lh_mo...@126.com> wrote: > On 2017/2/8 1:45, Ricardo Constantino wrote: > > Should be fixed with > > https://github.com/Alexpux/MINGW-packages/commit/ba282a67e, but I > thought > > someone would've reported it to upstream by now

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

Should be fixed with https://github.com/Alexpux/MINGW-packages/commit/ba282a67e, but I thought someone would've reported it to upstream by now? -- Check out the vibrant tech community on one of the world's most engaging

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)

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)

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

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

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

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