Thanks for the report.
On 02/20/2012 04:30 AM, Panther Martin wrote:
>
> I would also like to report 4 of 788 tests failed with Clang using:
>
> Mac OSX 10.7.3 Lion
> clang-3.1 (318)
> automake-1.11.3
> autoconf-2.68
> gawk-4.0.0
>
>
> Attached are my test results. I think
Thanks for the report.
On 02/20/2012 01:09 AM, Panther Martin wrote:
>
> Hi I'm reporting 1 test-suite failure on 64bit OSX Lion 10.7.3 using
>
> llvm-gcc-4.2.1 (5658)
> autoconf-2.68
> automake-1.11.3
> gawk-4.0.0
>
> FAIL: conffile-leading-dot.test (exit: 1)
> ===
I am having problems in Bison (current master) to recover
from a lost parse-gram.h, generated from parse-gram.y
with regular Automake (1.11.3) handling:
> AM_YFLAGS = -d -v --warnings=all,error --report=all
>
> src_bison_SOURCES = \
> ...
> src/output.h
Hi Akim.
On 02/20/2012 02:24 PM, Akim Demaille wrote:
> I am having problems in Bison (current master) to recover
> from a lost parse-gram.h, generated from parse-gram.y
> with regular Automake (1.11.3) handling:
>
>> AM_YFLAGS = -d -v --warnings=all,error --report=all
>>
>> src_bison_SOURCES =
Le 20 févr. 2012 à 14:58, Stefano Lattarini a écrit :
> Hi Akim.
Hi Stefano,
Thanks for the quick answer!
> The following patch extends a test which is aimed at checking
>>
>> this, but does it in a non-vpath build :)
>>
> But the test is wrong, because it checks that the Yacc-generated .h a
> On Feb 20, 2012, Stefano Lattarini wrote:
...
> The failure is here. I suspect this might be yet another timestamp issue.
> Could you please answer the following questions?
Yes I have a Core i5 8GB iMac.
No I there is no subsecond timestamp that I can see in touch or ls.
Yes it is rep
severity 10848 minor
tags 10848 patch
close 10848
thanks
On 02/20/2012 09:51 PM, Panther Martin wrote:
>
>
>> On Feb 20, 2012, Stefano Lattarini wrote:
> ...
>
>> The failure is here. I suspect this might be yet another timestamp issue.
>> Could you please answer the following questions?
Thanks for your relentless reporting.
On 02/20/2012 09:41 PM, Panther Martin wrote:
>
> These tests were running fine with only a few fails, but it came to a
> chunk of gcc tests and blew up.
>
Hmm... this doesn't ring a bell right away, even after I've looked into the
attached logs. Could you
