Closed paulhoule closed 10 years ago
I tried setting all locales to 'C', re-running autogen and all that and it still fails.
I did the build with Ubuntu 13.10 (had to also add gawk) on my own Virtualbox and did not encounter this problem. We have gcc 4.8.1, bison 2.7.12, and flex 2.5.35 and if I was going to blame anything it would be bison.
I did the build with Ubuntu 13.10 in AWS and it looks good.
We shall have to test this in-house on Ubuntu Trusty (14.04) , it could be a problem with the bison or one of the other tools required for the build ...
I checked Ubuntu 14.04 and it uses bison 3.0.2 which generates slightly different code for a reentrant parser. I updated getdate.y with some new directives to resolve this problem with bison v2.3 and above.
Patch 042f1427380e3a474581f4aa1ee064f5d2da9963 has been committed to both develop/6 and develop/7 branches
Is this going to be available in stable/7 in the near future? Is develop/7 usable for production?
Yes, it will be in stable/7 in the near further. Use of develop/7 in production is at your discretion and should be tested for your use case, but code committed to develop/7 has passed our internal test suites and thus we would say generally can be used ...
Hi, I've cloned stable/7 today and since I'm experiencing this issue I want to know If the fix is included there. thanks!
This is still an issue. Occurs under xubuntu 14.10.
Against develop/7 or stable/7 , as the fix is only in the former atm ?
I just fired up a Ubuntu Trusty instance in the AWS cloud and I go through the following sequence to build Virtuoso
it churns for a while and then it burns
How do I get a stable build that works? Here are some notes on the environment