[Top][All Lists]

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

RE: Bison 3.5.93 released [beta]

From: Jannick
Subject: RE: Bison 3.5.93 released [beta]
Date: Wed, 6 May 2020 11:28:55 +0200

Hi Akim,

On Mon, 4 May 2020 19:14:08 +0200, Akim Demaille wrote:
> Hi Jannick,
> > Le 4 mai 2020 à 09:50, Jannick <address@hidden> a écrit :

> > On Windows10/MSYS2 still two test failures - presumably EOL issues 
> > which, if I am not mistaken, cannot be solved by 'diff -u'.
> I'm not sure, given that you don't have the problem with the other 
> tests.  Yet I have no idea what's going on.

Testing against today's beta release 3.5.94 did not change anything, 

I investigated that the above mentioned failure does stem from an EOL issue, 
since adding in 'examples/test' the diff flag '--strip-trailing-cr' solved it.  
I used this flag to narrow down the problem, but this diff flag is not portable 
if I am not mistaken; at least it is not POSIX.  So a solution is required to 
either avoid system-depending EOL character(s) or to swallow them up somehow 
(using perhaps a sed script, dos2unix or alike in a portable fashion).  The way 
how output files are generated appears to matter, but I could not go deeper 
into the package to see what is happening.    

After all, the remaining test failure is bistromathic #13 (log attached).  I 
did not look into that in detail and I am not sure if this is an EOL issue 
again or of general nature.



Attachment: test-suite.log
Description: Binary data

reply via email to

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