search for: winsock_init

...H] daemon: program_name must be defined for Gnulib error module. --- daemon/guestfsd.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/daemon/guestfsd.c b/daemon/guestfsd.c index c67503e..b525db5 100644 --- a/daemon/guestfsd.c +++ b/daemon/guestfsd.c @@ -114,6 +114,9 @@ winsock_init (void) const char *sysroot = "/sysroot"; /* No trailing slash. */ int sysroot_len = 8; +/* Not used, but required by the gnulib 'error' module. */ +const char *program_name = "guestfsd"; + static void usage (void) { -- 1.6.5.2

.../brsfolder: Add shortcut to rename folders with the F2 key. shell32/brsfolder: Add shortcut to delete folders with the delete key. François Gouget (6): msxml3/tests: Make test_namespaces_as_attributes() static. mshtml: Make HTMLStyle_init_dispex_info() static. winhttp: Make winsock_init() static. winebus.sys: Add a trailing '\n' to a TRACE(). quartz/tests: Make testpin_{AddRef,Release}() static. wined3d: Modernize the macOS spelling. Gabriel Ivăncescu (20): shell32/autocomplete: Move the autocomplete processing and WM_KEYUP to separate functions....

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw This is the port to Windows using native Windows APIs (not MSYS or Cygwin). This patch series is at the point where it basically now works. I can run the server with the memory plugin, and access it remotely using guestfish, creating filesystems and so on without any apparent problems. Nevertheless there are many

Also available here: https://github.com/rwmjones/nbdkit/tree/2020-windows-mingw-nolib After a lot of work I have made the port to Windows work without using a separate library. Instead, on Windows only, we build an "import library" (library of stubs) which resolves references to nbdkit_* functions in the main program and fixes up the plugin, basically the first technique outlined in

https://bugzilla.redhat.com/show_bug.cgi?id=1477623 The first two patches are cleanups. The third patch changes the way that we handle Device and Dev_or_Path parameters so that a parameter marked as such can really only contain a block device name (and not, for instance, a chardev). Using a chardev here caused hangs in the API. The next two patches fix API usage to conform to this new stricter