Re: [PATCH] docs: mention cygwin shortcoming in

On 05/30/2013 11:29 AM, Eric Blake wrote: > I'm not quite ready to implement a replacement that > automatically works around this problem, since making the replacement > work for mingw seems much harder; so for now I'm just documenting > the issue I hit. > > * doc/posix-headers/sys_un.texi (sys/u

[PATCH] vasnprintf: silence mingw compiler warning

On mingw, vasnprintf is able to use snprintf, but not its return value; this led to a situation where gcc warns: vasnprintf.c: In function 'vasnprintf': vasnprintf.c:4609:21: error: variable 'has_width' set but not used [-Werror=unused-but-set-variable] Rather than hacking through a bunch of #if

[PATCH] docs: mention cygwin shortcoming in

I'm not quite ready to implement a replacement that automatically works around this problem, since making the replacement work for mingw seems much harder; so for now I'm just documenting the issue I hit. * doc/posix-headers/sys_un.texi (sys/un.h): Mention problem. Signed-off-by: Eric Blake ---

Re: regexp_exec thread-unsafe

Il 30/05/2013 02:59, Paul Eggert ha scritto: > On 05/26/2013 03:11 PM, Paolo Bonzini wrote: >> Use the lock module instead. > > Adding the lock module should work. But this will require > some reengineering of Guile, so that Guile uses the lock module > rather than its own thread packaging. Anot