autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug in AC_COMPUTE_INT


From: Lars J. Aas
Subject: Re: bug in AC_COMPUTE_INT
Date: Thu, 16 Nov 2000 13:06:28 +0100
User-agent: Mutt/1.2.5i

On Thu, Nov 16, 2000 at 12:51:05PM +0100, Akim Demaille wrote:
: 
: | I think I found it - checking now:
: | 
: | Index: aclang.m4
: | ===================================================================
: | RCS file: /cvs/autoconf/aclang.m4,v
: | retrieving revision 1.89
: | diff -u -r1.89 aclang.m4
: | --- aclang.m4   2000/11/14 11:06:37     1.89
: | +++ aclang.m4   2000/11/16 11:56:22
: | @@ -397,7 +397,7 @@
: |  # inclusion of `stdio.h'.
: |  m4_define([AC_LANG_INT_SAVE(C)],
: |  [AC_LANG_PROGRAM([m4_default([$1], address@hidden:@include "stdio.h"])],
: | -[FILE *f = fopen ("conftestval", "w");
: | +[FILE *f = fopen ("conftestval", "wb");
: 
: Portable?

Not really my cup of tea, but (from fopen(3) on Linux):

# The mode string can also include the letter ``b'' either as a third character 
or as a charĀ­
# acter between the characters in any of the two-character strings described 
above.  This  is
# strictly  for compatibility with ANSI C3.159-1989 (``ANSI C'') and has no 
effect; the ``b''
# is ignored.

: so how come we waited till today to discover this issue?

Running configure on the w32 platform hasn't really been common, nor is it
common yet either...

  Lars J



reply via email to

[Prev in Thread] Current Thread [Next in Thread]