On Tue, 30 Oct 2007, Bruno Haible wrote:
> Tim Rice wrote:
> > > The build fails on Caldera OpenLinux 3.1.1
> > > Here is a snipet of the build log
> > >
> > > make all-am
> > > make[2]: Entering directory `/usr/local/src/gnu/m4-1.3.10/lib'
> > > source='/opt/src/gnu/m4-1.4.10/lib/gl_array_l
Bruno Haible <[EMAIL PROTECTED]> writes:
> 2007-10-26 Bruno Haible <[EMAIL PROTECTED]>
>
> * lib/autoconf/types.m4 (_AC_TYPE_LONG_LONG_SNIPPET): New macro,
> extracted from AC_TYPE_LONG_LONG_INT and AC_TYPE_UNSIGNED_LONG_LONG_INT.
> (AC_TYPE_LONG_LONG_INT, AC_TYPE_UNSIGNED_LONG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 10/30/2007 7:29 PM:
> But for error-posix and verror-posix: Such a module would, on glibc systems,
> not only pull in vasnprintf but also replace the error() function. Do you
> really mean that?
Good question.
> Usually y
Eric Blake wrote:
> And we should probably do something similar by adding error-posix,
> verror-posix, and xvasprintf-posix. For example, m4 1.4.10 uses
> xvasprintf for its `format' builtin, and I had to manually pull in
> vasprintf-posix by looking at the implementation details of xvasprintf.c.
Jim Meyering wrote:
> > introduce a module 'xprintf-posix' that causes xprintf to have POSIX
> > semantics for the formatted output. It will depend on xprintf and
> > vprintf-posix. I'll do it later today if you don't beat me to it.
>
> That makes sense.
> It will be less invasive, too.
> Thanks.
Hi,
On Oct 30, 2007 10:27 PM, Micah Cowan <[EMAIL PROTECTED]> wrote:
>
> The "restrict" keyword, as used, is entirely appropriate for C code, as
> it is part of the C language. It is not part of the C++ language (at
> least not yet).
>
> It's a relatively recent addition to the C language, so the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Guy Rutenberg wrote:
> Since what version of GCC is the restricted keyword available? I've
> tried compiling the code with gcc ( 4.1.2) and it doesn't recognized
> this keyword. Compiling using gcc instead of g++ solved all compilation
> errors excep
Micah Cowan <[EMAIL PROTECTED]> writes:
> It's a relatively recent addition to the C language, so the restrict
> keyword is #defined to nothing for C compilers that don't support it
> (doesn't apply to modern GCC, which has supported it for a while, but
> _only_ when running as a C compiler).
G+
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Guy Rutenberg wrote:
> When trying to compile base64.c using g++ I got the following
> compilation problems:
Note that base64.c, .h are written in C, not C++. Trying to compile with
g++ makes almost as little sense as trying to compile it as Fortran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Guy Rutenberg wrote:
> I'm using gcc 4.1.2 on Gentoo. It may well be
Missing the rest of that sentence. :)
> N.B. I'm not subscribed to this list, so please cc back to my email your
> reply.
>Where can I find an email archive of this list?
Hi,
When trying to compile base64.c using g++ I got the following compilation
problems:
$ g++ -c base64.c
base64.c:44:20: error: config.h: No such file or directory
base64.h:34: error: expected ',' or '...' before 'in'
base64.h:39: error: expected ',' or '...' before 'in'
base64.c:67: error: expe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 10/30/2007 7:18 AM:
>> It's the xprintf.c code which calls vprintf(), bypassing printf(). Since
>> this is a detail that the gnulib user should not know about, we should
>> introduce a module 'xprintf-posix' that causes xpr
Bruno Haible <[EMAIL PROTECTED]> wrote:
>> >> freebsd$ ./printf %.2147483647f 1
>> >> Segmentation fault (core dumped)
>
> I reproduce on NetBSD 3.0, both with the system's printf program and with
> the coreutils printf.
>
> It dumps core for width 5000 but not for width 1000. Therfore
Hi Jim,
> >> freebsd$ ./printf %.2147483647f 1
> >> Segmentation fault (core dumped)
I reproduce on NetBSD 3.0, both with the system's printf program and with
the coreutils printf.
It dumps core for width 5000 but not for width 1000. Therfore I
think it's an unhandled out-of-memory c
Bruno Haible <[EMAIL PROTECTED]> wrote:
>> This is probably worth working around.
>> Maybe it's done already, but currently I've turned
>> off printf-posix in coreutils:
>>
>> freebsd$ ./printf %.2147483647f 1
>> Segmentation fault (core dumped)
>
> Before working around it in gnulib:
>
> - Wil
15 matches
Mail list logo
