bug-gnulib
[Top][All Lists]
Advanced

[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: Sat, 18 Sep 2021 11:04:38 -0600
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0

On 2021-09-18 09:10, Bruno Haible wrote:
Brian Inglis wrote:
Respun and applied patch successfully to glm4/threadlib.m4.

Did you regenerate the 'configure' script, and also do 'make distclean',
after patching threadlib.m4?

Find attached a new 'testdir-thread' package. When you configure and
build it (with './configure -C' and NO explicit setting of gl_cv_have_weak,
then "make && make check"), does it work? I.e. does it complete with just
one test failure (test-raise)?

I tried running make distclean in the build dir and it wiped all the files, before redoing the build. That seems to have done the trick. The configure output now only really mentions weak in comments, the build completes with no issues, and the checks complete with just that failure.

I was sure I had wiped the bison build dir with `cygport ... finish` just before rerunning `cygport ... all check`, but I have redone that, with the respun patch for the bison threadlib.m4, and without explicit gl_cv_have_weak, the configure output now shows guessing no, configure and build worked, the examples and tests are building YACC/CC/CCLD without dumping, so I am hopeful it will now pass the tests.

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.

--
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]