some problems with uClibc

2011-04-14 Thread Giuseppe Scrivano
Hello, During my attempt to port wget to uClibc-linux I have experienced a couple of problems with gnulib. 1) With an uClibc compiled without wchar support I had to include stddef.h in the wchar.h file. uClibc defines __GLIBC__ as well, so the previous guarded inclusion doesn't work. I had to

Re: some problems with uClibc

2011-04-14 Thread Bruno Haible
Hello Giuseppe, 1) With an uClibc compiled without wchar support I had to include stddef.h in the wchar.h file. uClibc defines __GLIBC__ as well, so the previous guarded inclusion doesn't work. I had to add: #ifdef __UCLIBC__ # include stddef.h #endif What was the problem exactly? In

Re: some problems with uClibc

2011-04-14 Thread Giuseppe Scrivano
Hi Bruno, Bruno Haible br...@clisp.org writes: 1) With an uClibc compiled without wchar support I had to include stddef.h in the wchar.h file. uClibc defines __GLIBC__ as well, so the previous guarded inclusion doesn't work. I had to add: #ifdef __UCLIBC__ # include stddef.h #endif

New stable snapshot

2011-04-14 Thread Ian Beckwith
Hi, I've released a new stable snapshot. See attached NEWS.stable for details. Tarball: http://erislabs.net/ianb/projects/gnulib/gnulib-20110412-stable.tar.gz Gitweb: http://erislabs.net/gitweb?p=gnulib.git;a=shortlog;h=refs/heads/stable Git: git://erislabs.net/gnulib.git tag: stable/20110412

Re: some problems with uClibc

2011-04-14 Thread Bruno Haible
Hi Giuseppe, Giuseppe Scrivano wrote: I get exactly the same error: make[4]: Entering directory `/tmp/testdir/gltests' g++ -DHAVE_CONFIG_H -I. -DGNULIB_STRICT_CHECKING=1 -I. -I. -I.. -I./.. -I../gllib -I./../gllib-MT test-wchar-c++.o -MD -MP -MF .deps/test-wchar-c++.Tpo -c -o

Re: writing to non-blocking pipes on Windows

2011-04-14 Thread Bruno Haible
On mingw, there was another test failure. Apparently the behaviour of write() on a non-blocking pipe fd depends on whether some pipe reader is currently blocked, read()ing from it. - If yes, then write() of more than the pipe buffer's size yield a partial write, no failure. - If no, then

reading from non-blocking pipes on Windows

2011-04-14 Thread Bruno Haible
The other failure of the non-blocking I/O on pipes test on mingw is because when read() is called on a non-blocking pipe fd with an empty buffer, it fails with EINVAL. Whereas POSIX says that it should fail with EAGAIN. This fixes it, by adding a 'read' module for the function read() and