[Top][All Lists]

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

Re: Bison testing on Solaris (with FAILURES)

From: Akim Demaille
Subject: Re: Bison testing on Solaris (with FAILURES)
Date: Wed, 3 Jul 2013 17:31:07 +0200

Le 28 juin 2013 à 11:40, Stefano Lattarini <address@hidden> a écrit :

>> I could disable the C++ tests at test-suite runtime if the C++
>> compiler is not happy with a simple #include <iostream>.
>> I could also try to disable the use of gnulib in our test suite.
>> Actually, since we are trying to check that our generated headers
>> work properly and are reasonably portable, that would make a lot
>> of sense.  However I don't remember why the test suite started
>> to use gnulib (it might even be by accident, I don't know), and I
>> don't plan to spend time on detaching the test suite from gnulib
>> right now.
>> Do you see options I missed?
> No, my knowledge of both C++ and the intertwining of Gnulib with
> the Bison testsuite is basically zero.  Sorry not to be of more
> help.

Well I tried to fix the problem with the appended patch.
Could you please try this tarball:


If the issue is not fixed with it (and I doubt it is), could you
please try


which has a difference approach?  Thanks in advance!

commit 8f9f1e749f10e11237839b90ce3e30e185c39821
Author: Akim Demaille <address@hidden>
Date:   Wed Jul 3 17:25:45 2013 +0200

    tests: beware of clashes between gnulib's <stdio.h> and native <stream>
    There are possible conflicts between gnulib replacement functions (in
    <stdio.h>) and their C++ wrappers (in <stream>).
    Reported by Stefano Lattarini.
    * tests/local.at (AT_DATA_SOURCE_PROLOGUE): Don't try to repair

diff --git a/tests/local.at b/tests/local.at
index e6afd36..6d3ac6b 100644
--- a/tests/local.at
+++ b/tests/local.at
@@ -339,17 +339,19 @@ m4_define([AT_LANG_DISPATCH],
-# ------------------------
+# -----------------------
 # The prologue that should be included in any source code that is
 # meant to be compiled.
 [[#include <config.h>
 /* We don't need perfect functions for these tests. */
+#undef getc
 #undef malloc
 #undef memcmp
 #undef realloc
 # ------------------------
 # The prologue that should be included in any grammar which parser is

reply via email to

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