Re: make getopt.c build in visual studio

2006-03-07 Thread Simon Josefsson
Eric Blake <[EMAIL PROTECTED]> writes: > According to Simon Josefsson on 3/7/2006 6:30 AM: >> Index: modules/unistd > ... >> + >> +# We need the following in order to create when the system >> +# doesn't have one. > > s/byteswap/unistd/ > > Other than that, thanks! Installed, thanks for the revi

Re: make getopt.c build in visual studio

2006-03-07 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Simon Josefsson on 3/7/2006 6:30 AM: > Index: modules/unistd ... > + > +# We need the following in order to create when the system > +# doesn't have one. s/byteswap/unistd/ Other than that, thanks! - -- Life is short - so eat dessert f

Re: gc.m4 and hard failure

2006-03-07 Thread Simon Josefsson
Simon Josefsson <[EMAIL PROTECTED]> writes: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > >> It would be great if the gc.m4 module could be taught not to fail when >> no random devices exist (as seen on hppa2.0-hp-hpux10.20). Passing >> >> --disable-random-device --disable-pseudo-random-devic

Re: play nice with AC_CACHE_CHECK

2006-03-07 Thread Simon Josefsson
Ralf Wildenhues <[EMAIL PROTECTED]> writes: > * readline.m4 (gl_FUNC_READLINE): Rewrite the cached part of the > test to be side-effect free by storing the result in the cache > variable gl_cv_lib_readline, and moving the assignment of > LIBREADLINE and LTLIBREADLIN

Re: gc.m4 and hard failure

2006-03-07 Thread Ralf Wildenhues
Hi Simon, * Simon Josefsson wrote on Tue, Mar 07, 2006 at 02:17:13PM CET: > Simon Josefsson <[EMAIL PROTECTED]> writes: > > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > >> It would be great if the gc.m4 module could be taught not to fail when > >> no random devices exist (as seen on hppa2.0-h

Re: make getopt.c build in visual studio

2006-03-07 Thread Simon Josefsson
[EMAIL PROTECTED] (Eric Blake) writes: >> With this, getopt actually do seem to compile and work in Visual >> Studio. Tested with the CLI in libtasn1, part of GnuTLS, with long >> options. >> >> I'll install this shortly unless someone protests. > > I'm not sure about this. Lately, the move has

Re: make getopt.c build in visual studio

2006-03-07 Thread Simon Josefsson
I forgot this diff in the last e-mail: Index: m4/unistd_h.m4 === RCS file: m4/unistd_h.m4 diff -N m4/unistd_h.m4 --- /dev/null 1 Jan 1970 00:00:00 - +++ m4/unistd_h.m4 7 Mar 2006 13:32:57 - @@ -0,0 +1,18 @@ +# unistd_h.

Re: `#error' vs string literal

2006-03-07 Thread Jim Meyering
Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > Another thing struck me: > > * Paul Eggert wrote on Wed, Mar 01, 2006 at 01:48:54AM CET: >> (AC_HEADER_STDBOOL): Don't assume "#error" works. Glad you spotted that. ... > This technique is not followed consistently in gnulib (unlike Autoconf). > I

Re: `#error' vs string literal

2006-03-07 Thread Ralf Wildenhues
Hi Jim, * Jim Meyering wrote on Tue, Mar 07, 2006 at 05:20:52PM CET: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > > | * md5.c: Use `#error' rather than a string literal to provoke > > failure. > > | * sha1.c: Likewise. > > > > I could not find corresponding discussion or bug

`#error' vs string literal (was: proposed gnulib-related additions to Autoconf)

2006-03-07 Thread Ralf Wildenhues
Another thing struck me: * Paul Eggert wrote on Wed, Mar 01, 2006 at 01:48:54AM CET: > (AC_HEADER_STDBOOL): Don't assume "#error" works. *snip* > Index: lib/autoconf/headers.m4 > === > RCS file: /cvsroot/autoconf/autoconf/lib/a

Re: `#error' vs string literal

2006-03-07 Thread Paul Eggert
Ralf Wildenhues <[EMAIL PROTECTED]> writes: > http://lists.gnu.org/archive/html/autoconf/2005-09/msg6.html Yes, that sounds familiar. The distinction here is that one should probably not rely on #error within .m4 tests, since the results of the tests might not be reliable. But within ordina

Re: make getopt.c build in visual studio

2006-03-07 Thread Martin Lambers
On Tue, 07. Mar 2006, 14:30:52 +0100, Simon Josefsson wrote: > diff -N modules/unistd > --- /dev/null 1 Jan 1970 00:00:00 - > +++ modules/unistd7 Mar 2006 13:30:18 - > @@ -0,0 +1,31 @@ > +Description: > +A for systems lacking it. > + > +Files: > +lib/unistd_.h > +m4/unistd_h.m4 > + > +

Re: gl_HEADER_UNISTD question

2006-03-07 Thread Paul Eggert
Juan Manuel Guerrero <[EMAIL PROTECTED]> writes: > When the bootstrap script is runned it produces the gl_HEADER_UNISTD > entry in the m4/gnulib.m4 file. For some reason this macro is not > expanded in the configure script. That's a bug in gnulib. I installed this patch: 2006-03-07 Paul Eggert

more unistd improvements

2006-03-07 Thread Paul Eggert
I installed these I-hope-obvious improvements to the unistd module. I didn't touch the modules Bruno maintains, which might also benefit from the unistd module. 2006-03-07 Paul Eggert <[EMAIL PROTECTED]> * MODULES.html.sh (Support for systems lacking POSIX:2001): Add unistd.