Hi Paolo,
> I'm seriously thinking of forking Wine's MSVCRT + gnulib's code to
> provide a decent native libc for Windows. That would support Windows CE
> of course.
Will this libc be interoperable with DLLs in the MS PE/COFF format? IMO this
would be essential. Microsoft's own Interix / Unix
Hello Ludovic,
> Libunistring 0.9.1 fails to build on Solaris with Sun cc and Sun make:
> cat: cannot open ../../lib/stdbool.mini.h
> *** Error code 2
This was a packaging bug in libunistring-0.9.1, and is fixed in
libunistring-0.9.1.1.
Bruno
Richard W.M. Jones wrote:
> error codes aren't compatible.
> Although Gnulib tries to define its own error numbers which are
> compatible with Win32 ones (eg. EINPROGRESS == 10036 ==
> WSAEINPROGRESS), it also uses some from the MinGW header files which
> are just plain wrong (eg. ENOMEM == 12 == E
FYI, while writing unit tests, I noticed this:
>From cf8ddf08dec79be620c011ce204cbdb6bff35c50 Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Sat, 28 Nov 2009 09:28:40 +0100
Subject: [PATCH] userspec: depend on the inttostr module, too
* modules/userspec (Depends-on): Add inttostr.
---
Change
On 11/27/2009 04:57 PM, Richard W.M. Jones wrote:
(b) A call to a Winsock socket function that gnulib hasn't replaced:
errno won't have any meaningful value and I must call WSAGetLastError.
We can add replacements for these.
(c) A call to a non-socket Win32 function that gnulib has replaced: