proposed stdbool fixes for AIX, HP-UX, and now IRIX

While looking into an old Bison bug report for IRIX I noticed that it would be fixed by the stdbool patches that have been suggested for gnulib. Any objections if I install them? Here they are again. They've been used in coreutils CVS for some time. 2005-12-13 Paul Eggert <[EMAIL PROTECTED]>

argp-fmtstream.h, localcharset.c

It seems gnulib changes have been made to argp-fmtstream.h, localcharset.c, previously synced from libc and gettext-runtime respectively. Should I comment out the sync, or? Thanks, k ___ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org

Re: $(EXEEXT) in TESTS required?

[ Cc:ing bug-automake; this is http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/5240 ] Hi Simon, * Simon Josefsson wrote on Thu, Jan 19, 2006 at 10:50:43AM CET: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > * Simon Josefsson wrote on Thu, Jan 19, 2006 at 09:42:17AM CET: > >> > >> It doesn

Re: getaddrinfo: finding gethostbyname in mingw32

The follow patch make getaddrinfo work (it seems Windows has a getaddrinfo implementation, although it doesn't have gai_strerror) _except_ that applications need to initialize Windows' socket code manually, by calling WSAStartup. I'm not sure how to handle that. One solution is to create gl_getadd

socklen_t (was: Re: inet_ntop fix for mingw32)

This seem to work on all platforms I have tested (including mingw32), so I have installed it. This version doesn't duplicate the socket module as much anymore. Arguable, it would be more correct to replace #if HAVE_SYS_SOCKET_H # include #endif #if HAVE_WS2TCPIP_H

socket.h

For some reason, mingw32 uses non-POSIX names for shutdown's 'how'. I have installed this. 2006-01-19 Simon Josefsson <[EMAIL PROTECTED]> * socket_.h: Map SHUT_RD, SHUT_WR, SHUT_RDWR correctly. --- socket_.h 09 Jan 2006 17:13:09 +0100 1.1 +++ socket_.h 19 Jan 2006 14:39:07

Re: making fts thread-safe (no more fchdir)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Jim Meyering on 1/19/2006 3:39 AM: > > As I said, I'm reluctant to add this complexity, > without some evidence that it will be used. How about a simpler patch to gnulib: define FTS_CWDFD, then make gnulib fts_open() fail unless FTS_CWDF

tls-tests and lock-tests

How about this? Index: ChangeLog === RCS file: /sources/gnulib/gnulib/ChangeLog,v retrieving revision 1.478 diff -u -p -r1.478 ChangeLog --- ChangeLog 19 Jan 2006 09:05:56 - 1.478 +++ ChangeLog 19 Jan 2006 13:11:35 -

Re: making fts thread-safe (no more fchdir)

I wrote: > FYI, I did most of the work to add FTS_CWDFD, just to see -- and it's > not so bad, but the result is certainly less maintainable. After saying the above, I figured I should produce the actual code, so here it is. For now at least, I don't plan to check in these changes. This patch re

Re: [bug-gnulib] $(EXEEXT) in TESTS required?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bruno Haible on 1/18/2006 12:57 PM: > > Thanks for catching that! I suspect that many packages have the same > problem, because it appears only with the mingw platform. (No problem > with cygwin.) Cygwin had no problem in this particular

Re: $(EXEEXT) in TESTS required?

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hi Simon, > > * Simon Josefsson wrote on Thu, Jan 19, 2006 at 09:42:17AM CET: >> >> It doesn't seem to matter if I change noinst_PROGRAMS into >> check_PROGRAMS, I still have to add $(EXEEXT) to the binaries in TESTS >> for things to work. >> >> TESTS

Re: $(EXEEXT) in TESTS required?

Hi Simon, * Simon Josefsson wrote on Thu, Jan 19, 2006 at 09:42:17AM CET: > > It doesn't seem to matter if I change noinst_PROGRAMS into > check_PROGRAMS, I still have to add $(EXEEXT) to the binaries in TESTS > for things to work. > > TESTS += test-gc > check_PROGRAMS = test-gc > > => > > make

Re: $(EXEEXT) in TESTS required?

I installed this. 2006-01-19 Simon Josefsson <[EMAIL PROTECTED]> * gnulib-tool: Set check_PROGRAMS. * modules/arcfour-tests, modules/arctwo-tests, modules/crc-tests, modules/des-tests, modules/gc-arcfour-tests, modules/gc-arctwo-tests, modules/gc-des-tests, mo

Re: $(EXEEXT) in TESTS required?

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hi Simon, > > * Simon Josefsson wrote on Wed, Jan 18, 2006 at 02:01:27PM CET: >> While testing mingw32 portability (GNU SASL now builds cleanly >> cross-compiled to mingw32!) I encountered the following. It seems >> $(EXEXT) is required for automake