[Top][All Lists]

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

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

From: Brian Inglis
Subject: Re: bison segv under Cygwin 64 at fatal-signal.c:318
Date: Thu, 23 Sep 2021 11:54:08 -0600
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0

On 2021-09-20 21:25, Akim Demaille wrote:
Le 18 sept. 2021 à 19:04, Brian Inglis a écrit :
Thanks very much for your help Bruno, in diagnosing the issue
correctly, and providing the patch: I will ensure your patch comment
gets prefixed into the respun bison gnulib patch.
And thanks Akim for getting Bruno involved to address the right area.
Cygwin bison users will be happy having the latest build available.

I did not see the confirmation that the last tarball I made did work on your 
I might have missed it though.

Sorry Akim,

I thought it was understood as confirmed in my last message.

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.

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

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.

Thanks very much again to you both, the great help is appreciated.

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

reply via email to

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