Hello all, I posted a while ago about my issue of hanging bison on more than one tru64 5.1b systems.
I tried a couple more things to make sure and have more details to give. I had compiled an older version before with gcc but it wouldn't work either. Now I just tried again building bison 2.4.1 with gcc 4.0.2 and the exact same thing happen with the same tests: ## --------------------------- ## ## GNU Bison 2.4.1 test suite. ## ## --------------------------- ## Input Processing. 1: Invalid $n and @n ok 2: Type Clashes ok 3: Unused values If I kill off the hanging test, it will hang again on the next one, although a few will pass (very few, always the same of course). I tried disabling optimization, both with gcc and native compilers but that doesn't change anything. Of course if I install despite the failed tests, bison will hang when used later in the same manner. I tried disabling the available flex and older bison in the system while building the new bison, just in case any of them would cause something, but no difference either. I'm not a C developer and I'm not fully versed in using the debuggers, so I need guidance to track this issue properly. What can I try next? Thanks all, -- Didier Godefroy mailto:[email protected] Support anti-Spam legislation. Join the fight http://www.cauce.org/
