Re: [Mingw-w64-public] Broken linker in gcc?

2022-08-23 Thread Carl Kleffner
Hi, I got exactly this error trying to include a MS Visual C build library during the link process. If this library contains a .voltbl section you will encounter this error. Maybe something of this kind is in your path to the libraries you don't get while manually running the link command. best r

[Mingw-w64-public] Broken linker in gcc?

2022-08-23 Thread Julian Waters
Recently upgraded to ucrt gcc 12 and I'm getting "This app can't run on your PC" prompts when I attempt to run binaries compiled by ucrt linking gcc (A quick look at dependency walker reveals this is actually error 193 - The executable is not a valid Win 32 application) which suggests a bad PE form

Re: [Mingw-w64-public] Broken FreeAddrInfoEx in ws2tcpip.h

2019-03-01 Thread LRN
On 01.03.2019 10:14, Liu Hao wrote: > 在 2019/2/11 下午6:34, Liu Hao 写道: >> 在 2019/2/8 19:59, Liu Hao 写道: >>> 在 2019/2/8 上午4:41, LRN 写道: ws2tcpip.h declares: WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExA(PADDRINFOEXA pAddrInfo); WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExW(PADDRINF

Re: [Mingw-w64-public] Broken FreeAddrInfoEx in ws2tcpip.h

2019-02-28 Thread Liu Hao
在 2019/2/11 下午6:34, Liu Hao 写道: > 在 2019/2/8 19:59, Liu Hao 写道: >> 在 2019/2/8 上午4:41, LRN 写道: >>> ws2tcpip.h declares: >>> WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExA(PADDRINFOEXA pAddrInfo); >>> WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExW(PADDRINFOEXW pAddrInfo); >>> >>> however of these t

Re: [Mingw-w64-public] Broken FreeAddrInfoEx in ws2tcpip.h

2019-02-18 Thread Liu Hao
在 2019/2/18 23:45, JonY via Mingw-w64-public 写道: > > I thought of removing FreeAddrInfoExA completely from the header, but I > don't know if there are code relying on it. > > > It would be feasible if we apply the same to the `GetEnvironmentStrings()` function [1], which suffers from the same

Re: [Mingw-w64-public] Broken FreeAddrInfoEx in ws2tcpip.h

2019-02-18 Thread JonY via Mingw-w64-public
On 2/18/19 12:52 PM, Liu Hao wrote: > 在 2019/2/11 下午6:34, Liu Hao 写道: >> 在 2019/2/8 19:59, Liu Hao 写道: >>> 在 2019/2/8 上午4:41, LRN 写道: ws2tcpip.h declares: WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExA(PADDRINFOEXA pAddrInfo); WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExW(PADDRINF

Re: [Mingw-w64-public] Broken FreeAddrInfoEx in ws2tcpip.h

2019-02-18 Thread Liu Hao
在 2019/2/11 下午6:34, Liu Hao 写道: > 在 2019/2/8 19:59, Liu Hao 写道: >> 在 2019/2/8 上午4:41, LRN 写道: >>> ws2tcpip.h declares: >>> WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExA(PADDRINFOEXA pAddrInfo); >>> WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExW(PADDRINFOEXW pAddrInfo); >>> >>> however of these t

Re: [Mingw-w64-public] Broken FreeAddrInfoEx in ws2tcpip.h

2019-02-11 Thread Liu Hao
在 2019/2/8 19:59, Liu Hao 写道: > 在 2019/2/8 上午4:41, LRN 写道: >> ws2tcpip.h declares: >> WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExA(PADDRINFOEXA pAddrInfo); >> WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExW(PADDRINFOEXW pAddrInfo); >> >> however of these two functions only the latter exists in w

Re: [Mingw-w64-public] Broken FreeAddrInfoEx in ws2tcpip.h

2019-02-08 Thread Liu Hao
在 2019/2/8 上午4:41, LRN 写道: > ws2tcpip.h declares: > WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExA(PADDRINFOEXA pAddrInfo); > WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExW(PADDRINFOEXW pAddrInfo); > > however of these two functions only the latter exists in ws2_32.dll. The > former > is actual

[Mingw-w64-public] Broken FreeAddrInfoEx in ws2tcpip.h

2019-02-07 Thread LRN
ws2tcpip.h declares: WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExA(PADDRINFOEXA pAddrInfo); WINSOCK_API_LINKAGE void WSAAPI FreeAddrInfoExW(PADDRINFOEXW pAddrInfo); however of these two functions only the latter exists in ws2_32.dll. The former is actually named FreeAddrInfoEx, without the "A" s

Re: [Mingw-w64-public] broken

2013-11-23 Thread Ruben Van Boxem
2013/11/23 Óscar Fuentes > Hello Ruben, > > Ruben Van Boxem > writes: > > > This is comparable to the output I get from VS2013. So I would say this > is > > a quality of implementation issue (wrt the resolution of the clock > used). > > I doubt though that this is nonconformant. I didn't look u

Re: [Mingw-w64-public] broken

2013-11-23 Thread Óscar Fuentes
Hello Ruben, Ruben Van Boxem writes: > This is comparable to the output I get from VS2013. So I would say this is > a quality of implementation issue (wrt the resolution of the clock used). > I doubt though that this is nonconformant. I didn't look up the exact > chrono requirements in the stan

Re: [Mingw-w64-public] broken (was: Coverage of C++11 library features)

2013-11-23 Thread Ruben Van Boxem
2013/11/23 Óscar Fuentes > Ruben Van Boxem > writes: > > > The libstdc++ online documentation keeps a list here: > > http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html > > > > This should correspond fairly well to what is available on any platform. > Of > > course, there may be deviation

[Mingw-w64-public] broken (was: Coverage of C++11 library features)

2013-11-23 Thread Óscar Fuentes
Ruben Van Boxem writes: > The libstdc++ online documentation keeps a list here: > http://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html > > This should correspond fairly well to what is available on any platform. Of > course, there may be deviations (e.g. , and std::to_string in the > past).

Re: [Mingw-w64-public] broken dshow in dx-sdk

2010-02-20 Thread NightStrike
On Thu, Feb 11, 2010 at 6:55 PM, Ozkan Sezer wrote: > On Thu, Feb 11, 2010 at 11:21 PM, Kai Tietz wrote: >> 2010/2/11 Ozkan Sezer : >>> Regarding this thread from today: >>> http://sourceforge.net/projects/mingw-w64/forums/forum/723798/topic/3550908 >>> >>> Our dshow.h (seems to be based on an ol

Re: [Mingw-w64-public] broken dshow in dx-sdk

2010-02-11 Thread Ozkan Sezer
On Thu, Feb 11, 2010 at 11:21 PM, Kai Tietz wrote: > 2010/2/11 Ozkan Sezer : >> Regarding this thread from today: >> http://sourceforge.net/projects/mingw-w64/forums/forum/723798/topic/3550908 >> >> Our dshow.h (seems to be based on an old wine version) >> is broken due to missing extra headers th

Re: [Mingw-w64-public] broken dshow in dx-sdk

2010-02-11 Thread Kai Tietz
2010/2/11 Ozkan Sezer : > Regarding this thread from today: > http://sourceforge.net/projects/mingw-w64/forums/forum/723798/topic/3550908 > > Our dshow.h (seems to be based on an old wine version) > is broken due to missing extra headers that it depends > on. > > I included the lastest versions fro