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 mentioned that I had forgot something in PKGBUILD and he fixed it a little. I pulled the new script but didn't test it. I guess it is the removal of the two command line options that might be the cause of this problem, because I don't split packages and the file `libstdc++.a` in question has been installed into a slightly different directory ("C:\MinGW\MSYS2\mingw64\lib\libstdc++.a") and I don't have this problem. But we had better ask alexey for sure. ------------------ Best regards, lh_mouse 2016-07-24 ------------------------------------------------------------- 发件人：Ricardo Constantino <[email protected]> 发送日期：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 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.1.0\libstdc++.a" | grep "cow-stdexcept.o" cow-stdexcept.o: file format pe-x86-64 ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Msys2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/msys2-users
