Yeah - I tend to run into bugs early because I keep my environment up to date
It's been challenging on Cygwin in the past because many packages especially 
toolchains were neglected - recently it's been a very pleasant surprise to see 
GCC being kept up - and I've been building on Cygwin a lot more
    On Friday, July 11, 2025 at 10:10:54 AM CDT, Bruno Haible <br...@clisp.org> 
wrote:  
 
 Z. Majeed wrote:
>  Spotting the diff was trivial - it's caused by an idempotency check for 
>stddef.h that was added to gnulib in commit e529f4f on 8 April 2025

(Workaround to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114870 )

I see. Yes, this explains why (with the bison state as of two days ago)
I see no problem with gcc < 15 and you saw the problem with gcc >= 15.

> Until there's a new Bison release the fix is to use source since Paul's 
> update commit 2ceaf03

Thanks for finding out.

I'll set up a CI for Bison, so as to see how the current Bison sources
behave on other platforms than Cygwin.

Bruno

  

Reply via email to