Andreas Schwab <[EMAIL PROTECTED]> wrote:
> > The gl_C_COMPOUND_LITERALS test can never succeed, since the test
> > program is invalid C. A compound literal is never a constant
> > expression, thus cannot be used to initialize a static variable.
Thanks for the patch. Since it's not obvious that t
Bruno Haible wrote:
Eric Blake wrote:
According to Albert Chin on 6/20/2008 5:49 PM:
| Trying to run the testsuite for the vasprintf-posix module on HP-UX
| 10.20 using the HP C compiler:
| $ ./gnulib-tool --test --with-tests vasprintf-posix
| ...
| PASS: test-EOVERFLOW
| PASS: test-allo
Added wdiff-bugs. The previous messages in this thread:
http://lists.gnu.org/archive/html/bug-gnulib/2008-06/msg00264.html
http://lists.gnu.org/archive/html/bug-gnulib/2008-06/msg00271.html
On Tue, Jun 24, 2008 at 7:00 AM, Bruno Haible <[EMAIL PROTECTED]> wrote:
> Ludovic Courtès wrote:
>> You pr
Andreas Schwab <[EMAIL PROTECTED]> wrote:
> The gl_C_COMPOUND_LITERALS test can never succeed, since the test
> program is invalid C. A compound literal is never a constant
> expression, thus cannot be used to initialize a static variable.
Hi Andreas,
Thanks for the patch. It looks fine.
Howeve
The gl_C_COMPOUND_LITERALS test can never succeed, since the test
program is invalid C. A compound literal is never a constant
expression, thus cannot be used to initialize a static variable.
Andreas.
2008-06-24 Andreas Schwab <[EMAIL PROTECTED]>
* m4/getdate.m4 (gl_C_COMPOUND_LITERAL
Ludovic Courtès wrote:
> You probably already thought about it, but why not use `wdiff' for that?
I think before you can recommend wdiff,
1) there should be a release on ftp.gnu.org that does not dump core at
every invocation, (*)
2) the program should support colorized output like we kno
Hi,
Eric Blake <[EMAIL PROTECTED]> writes:
> On m4, I'm currently playing with multiple branches, each of which has
> imported
> a different set of gnulib modules via 'gnulib-tool --import'. I'm finding it
> very difficult to track which modules have been imported to which branches by
> usin
Eric Blake <[EMAIL PROTECTED]> wrote:
> According to Jim Meyering on 6/23/2008 2:12 AM:
> | 83ASSERT (old_sa.sa_flags == 0);
> |
> | And the value of old_sa.sa_flags is 0x400,
> | which happens to be SA_RESTORER.
>
> Ah. An extension flag, not defined by POSIX. In short, gnulib can't
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Eric Blake asked:
>> Should the open-safer module depend on open?
>
> Yes, I think fcntl-safer should depend on 'open'.
>
> Jim, your opinion?
Yes, most definitely.
There are a few other modules that may call open in such a way
(for writing, and with an ar
