[Top][All Lists]

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

Re: bison-2.6 released [stable]

From: Hans Aberg
Subject: Re: bison-2.6 released [stable]
Date: Fri, 20 Jul 2012 10:53:56 +0200

On 20 Jul 2012, at 09:58, Akim Demaille wrote:

> Thanks for trying it.

You are welcome. I thought I'd check clang, as the LLVM-GCC that is pointed to 
by /usr/local/gcc is very slow, and will be removed in a future Xcode release I 

> Le 19 juil. 2012 à 18:56, Hans Aberg a écrit :
>> On 19 Jul 2012, at 16:37, Akim Demaille wrote:
>>> Bison 2.6 is born, the parents are well, and happy.
>> I ran this on Mac OS X 10.7.4 where using the system compiler clang 
>> (llvm-gcc whic is pointe to by /usr/bin/gcc is now deprecated) supplied by 
>> Xcode 4.3.3, and I go the strange warning below by the following command 
>> sequence:
>> Build without the source tree using
>> $ tar -xf bison-2.6.tar.xz 
>> $ mkdir build-2.6
>> $ cd build-2.6/
>> $ export CC=/usr/bin/clang CXX=/usr/bin/clang++
>> $ ../bison-2.6/configure 
>> $ make
>> Then start a new shell where CC and CXX are not defined, in which 'make 
>> check' produces the first warnings below.
>> After that, in the original shell CC are defined, 'make check' produces the 
>> second warnings and  ending with '0 tests were successful.
> I cannot reproduce it following your script.  BTW, I believe the
> mkdir is useless, and ./configure would suffice: you seem to build
> in place.

It is required when building GCC, and the developers get quite upset when 
people still try to use ./configure. So I wanted to try it out, even though it 
is not a requirement for Bison.

> Given the nature of the messages:
>> 268: Absolute namespace references                  
>> /usr/local/src/bison/build-2.6/tests/testsuite.dir/at-groups/268/test-source:
>>  line 1157: 
>> /usr/local/src/bison/build-2.6/tests/testsuite.dir/at-groups/268/status: No 
>> such file or directory
>> testsuite: WARNING: unable to parse test group: 268
>> testsuite: WARNING: A failure happened in a test group before any test could 
>> be
>> testsuite: WARNING: run. This means that test suite is improperly designed.  
>> Please
>> testsuite: WARNING: report this failure to <address@hidden>.
>> ../../bison-2.6/tests/testsuite: line 1984: 
>> /usr/local/src/bison/build-2.6/tests/testsuite.dir/at-groups/268/check-line: 
>> No such file or directory
>> cat: 
>> /usr/local/src/bison/build-2.6/tests/testsuite.dir/at-groups/268/check-line: 
>> No such file or directory
>> ../../bison-2.6/tests/testsuite: line 2021: 
>> /usr/local/src/bison/build-2.6/tests/testsuite.dir/at-groups/268/fail: No 
>> such file or directory
>> FAILED ()
> I wonder if you did not have say two "make check" running concurrently?
> Maybe one of them, for some unknown reason, rewrote "testsuite" while
> the other one was running it?

I reran it now from one shell and it passed:
## ------------- ##
## Test results. ##
## ------------- ##

308 tests were successful.
7 tests were skipped.

> What's the result of "wc tests/testsuite"?  I have
>  164175  551986 5095566 tests/testsuite

In this test, I got:
  $ wc tests/testsuite.log 
     517    4004   34775 tests/testsuite.log

Returning to the stuff above: on Mac OS X, in Terminal, after 'make' and 'make 
pdf', I created a new Tab before doing 'make check', which creates a new shell 
from scratch, though set to the same directory. But then the CC and CXX 
variables are undefined in this new shell. I then saw the first set of warnings 
I posted. Then I started another 'make check' in the original directory, with 
CC and CXX, that did indeed run concurrently with the first one, but my 
assumption was that because of the delay, it should not interfere.


reply via email to

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