Re: bison segv under Cygwin 64 at fatal-signal.c:318

Akim Demaille <[email protected]> Fri, 24 Sep 2021 05:28:24 +0200
Newsgroups gmane.comp.parsers.bison.bugs
Message-ID <[email protected]>
Hi Brian, [dropping bug-gnulib]

> Le 23 sept. 2021 à 19:54, Brian Inglis <[email protected]> a écrit :
> 
> Sorry Akim,
> 
> I thought it was understood as confirmed in my last message.

You might very well have, but I didn't see it.  I saw a confirmation of success of a tarball that I interpreted as referring to Bruno's testdir-thread, but maybe you meant bison.


> This month I am busy dealing with a number of maintained package upgrade build and test failures, and at least one other appears to also be due to an obscure gnulib upgrade, after years of upgrades with at most only the occasional package tweak required, requiring only basic knowledge of autotools and none of gnulib!
> With each build requiring one or more hours for the package manager to configure && make && make VPATH install && make check locally, for each arch, then repeat for confirmation on the CI, it takes up a lot of free time.

I sure understand this.

> Your interim release includes the gnulib threadlib.m4 patch, so I had to disable applying that, which is great.

Great.  Then we have Bison 3.8.2.  I'll do that this weekend.

> Cygwin only needs the revert-autoconf-upgrade patch, until an experienced autotools user adopts the autotools as maintainer and provides upgrades.
> 
> The builds and tests run completely, and only the Doxygen tests fail, although the doc builds work: not a significant concern.

I could have a look at that.  Please send the logs.

Cheers!