[EMAIL PROTECTED] (Eric Blake) writes:
Bruno, is it okay to apply this?
2006-06-14 Eric Blake [EMAIL PROTECTED]
* ssize_t.m4 (gt_TYPE_SSIZE_T): Work in spite of -Werror.
I'm not Bruno, but yes, please apply that. Thanks.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 6/15/2006 1:32 AM:
[EMAIL PROTECTED] (Eric Blake) writes:
Bruno, is it okay to apply this?
2006-06-14 Eric Blake [EMAIL PROTECTED]
* ssize_t.m4 (gt_TYPE_SSIZE_T): Work in spite of -Werror.
Applied.
I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Santiago Vila on 6/15/2006 2:53 AM:
We are getting closer:
$ cd m4
$ ./configure CFLAGS=-Wall LOG-configure
$ make CFLAGS='-Wall -Werror' LOG-make
make[3]: Entering directory `/home/sanvila/tmp/m4/lib'
gcc -DHAVE_CONFIG_H -I.
Hi Folks,
The CVS project found a need to add the following patch to
lib/strtoimax.c in order to get compilation on Windows to work.
The basic problem is that there is an __int64 type and three conversion
functions:
char * _i64toa(__int64, char *, int);
char * _ui64toa(unsigned __int64, char *,
[Sorry about sending a reverse patch the first time around...]
Hi Folks,
The CVS project found a need to add the following patch to
lib/strtoimax.c in order to get compilation on Windows to work.
The basic problem is that there is an __int64 type and three conversion
functions:
char *
Mark D. Baushke [EMAIL PROTECTED] writes:
but 'long long' is NOT available.
That's weird, since it's been part of the C standard for 7 years. Are
the Microsoft Windows C compilers that far behind the times? Or
perhaps they just need to set some compiler switch to make 'long long'
available?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Eggert [EMAIL PROTECTED] writes:
I'm getting a bit lost with info about both stdint.h versus
inttypes.h, but does the following patch fix the problem?
This does not fix the problem as the
AC_CACHE_VAL(gl_cvs_header_stdint_h) is interfering
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Eggert wrote:
Mark D. Baushke [EMAIL PROTECTED] writes:
but 'long long' is NOT available.
That's weird, since it's been part of the C standard for 7 years. Are
the Microsoft Windows C compilers that far behind the times?
PMFJI - I'm