Re: [Mingw-w64-public] [PATCH] crt: Add DnsCleanupTcpConnections to dnsapi

2023-12-13 Thread Gisle Vanem via Mingw-w64-public
Mark Harmstone wrote: diff --git a/mingw-w64-crt/lib-common/dnsapi.def b/mingw-w64-crt/lib-common/dnsapi.def index 929deecd6..fae00a0a5 100644 --- a/mingw-w64-crt/lib-common/dnsapi.def +++ b/mingw-w64-crt/lib-common/dnsapi.def @@ -28,6 +28,7 @@ DnsAsyncRegisterTerm DnsCancelQuery

Re: [Mingw-w64-public] Determining mingw runtime version

2022-03-06 Thread Gisle Vanem
sisyphus wrote: Is there a simple command that I can run to see the (mingw-w64) runtime version number - something akin to "gcc -dumpversion" ? A command that displays only the value of __MINGW64_VERSION_MAJOR would probably suffice. Some .bat-file with: setlocal set

Re: [Mingw-w64-public] ld.exe or link.exe bug?

2021-12-29 Thread Gisle Vanem
Martin Storsjö wrote: In the meantime, when you create your regular import library with an option like -Wl,--out-implib,libfoo.dll.a, add the option -Wl,--output-def,foo.def. After that, run "dlltool -d foo.def -l libfoo.dll.a". This recreates the import library in a form that works better

[Mingw-w64-public] ld.exe or link.exe bug?

2021-12-29 Thread Gisle Vanem
Hello Gnu exports. I ned help figuring out an issue with using a set of MinGW generated import libraries in a MSVC program (called 'hsmodem.exe'; "High-sped Modem"). I'm not using MinGW-w64, but TDM-gcc (gcc 10.3.0). Hopefully they are similar in this regard. I've built these using MinGW (which

[Mingw-w64-public] Figuring out unused libraries

2020-03-28 Thread Gisle Vanem
Hello list and GNU-experts. When linking a gcc program, I'd like figure out if a library is needed or not. I mean, when generating a .map-file with -Wl,--print-map,--cref, I cannot see a report of libraries that are not need for a correct link. Is there a way to tell. Similar to what MSVC's

Re: [Mingw-w64-public] lock an empty file?

2020-01-10 Thread Gisle Vanem
David Mathog wrote: The test program just tries to lock, and then unlock that file.  It should do so 3 only after the subprocess releases its lock. Have you tried '_locking()' or '_lock_file()' for your Windows version? Ref:

Re: [Mingw-w64-public] 32-bit off_t on x86_64

2018-08-04 Thread Gisle Vanem
LRN wrote: We've got a complaint about crashes when using g_stat() in glib. Debugging showed that sizeof stat.st_size == 4 in user application, but sizeof stat st_size == 8 in glib. Turns out, MinGW-w64 defines 'off_t' (the type of st_size) as a synonym for 'long', and 'long' is always[1]

Re: [Mingw-w64-public] [Project News|New Builds]

2017-07-24 Thread Gisle Vanem
niXman wrote: The new builds of MinGW-W64 based on GCC-7.1.0 is uploaded. MinGW-w64 v5.x is used. Do any of these support '-m32' *and* '-m64'? I guess not, since on SF I see a directory-branch named "Multilib Toolchains(Targetting Win32 and Win64)" which is a bit old. -- --gv

Re: [Mingw-w64-public] [Bulk] windres option for -march?

2016-04-13 Thread Gisle Vanem
Julien Darthenay wrote: > But I am unable to find the > options to use with "windres" to build the resource object file. Are > there any "windres" option to use to target 64-bit and 32-bit ? What I do in such case is: RCFLAGS = -O COFF ifeq ($(BUILD_64BIT),1) RCFLAGS += --target=pe-x86-64

[Mingw-w64-public] Win-10 Anniversary Edition

2016-04-01 Thread Gisle Vanem
The upcoming Win-10 "Anniversary Edition" (build 2016?), promises running "Ubuntu in Userspace" on Windows. Nice! Release-date seems to be in June. Here are some details: http://insights.ubuntu.com/2016/03/30/ubuntu-on-windows-the-ubuntu-userspace-for-windows-developers/

Re: [Mingw-w64-public] Differentiate on MinGW-w64 and TDM-gcc

2016-03-19 Thread Gisle Vanem
Ruben Van Boxem wrote: > There is, as far as I know, no special define you can check to differentiate > TDM's GCC from vanilla GCC. If I remember > correctly, there's no extra defines added into the compiler in the patches > applied in a TDM build. Thanks for clearing that up. -- --gv

Re: [Mingw-w64-public] Differentiate on MinGW-w64 and TDM-gcc

2016-03-19 Thread Gisle Vanem
I wrote: > In a 32-bit program if mine (while printing the version info) > I have stuff like: > > extern const char *os_name (const char *vendor); > > #if defined(__MINGW64_VERSION_MAJOR) >#define VENDOR os_name ("MinGW-w64") /* a new-school MinGW */ > #elif defined(__MINGW32__) >

[Mingw-w64-public] Differentiate on MinGW-w64 and TDM-gcc

2016-02-25 Thread Gisle Vanem
Hello list. In a 32-bit program if mine (while printing the version info) I have stuff like: extern const char *os_name (const char *vendor); #if defined(__MINGW64_VERSION_MAJOR) #define VENDOR os_name ("MinGW-w64") /* a new-school MinGW */ #elif defined(__MINGW32__) #define VENDOR

Re: [Mingw-w64-public] Cross-compiling with MinGW-w64

2015-08-25 Thread Gisle Vanem
Alexandre Pereira Nunes wrote: See tdm-gcc, it works like that. I know (that's why I love TDM-gcc). But according to my: f:\MingW32\MingW-w64\bin\gcc.exe -v --help MingW-w64 could do that too: -m32 Generate 32bit i386 code -m64 Generate 64bit x86-64 code I was under the

Re: [Mingw-w64-public] Strange linker error with gcc-5.1 32-bit involving 'virtual thunk'

2015-07-30 Thread Gisle Vanem
Edward Diener wrote: If I remove the declaration and definition of ex_xml_exception::what(), since it is not needed, when linking I get: throw_exception_ex.o:throw_exception_ex.cpp:(.rdata$_ZTV16ex_xml_exception[__ZTV16ex_xml_exception]+0x20): undefined reference to `virtual thunk to