Boolector: Upgrade to 3.0.0

[marcogario]

Updated installer for boolector 3.0.0. This does not include any new feature.

[marcogario]

I would wait to merge this until upstream accepts Boolector/boolector#9 .
Then we will need to change the installer into a git based installer.

I wanted to prepare the PR so that we can run all the tests, and maybe start looking into integrating some of the new features.

[aniemetz]

Boolector/boolector#9 is merged in. Thanks for reporting and providing a fix!

[marcogario]

The current CI fails because of the following error:

python -c "import pyboolector"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: /home/travis/virtualenv/python2.7.14/lib/python2.7/site-packages/pyboolector.so: undefined symbol: PyFPE_jbuf

I think this might be due to a mismatch between the system python and the venv python.

Edit: Indeed, the configure says:

-- Found PythonInterp: /home/travis/virtualenv/python2.7.14/bin/python (found version "2.7.14") 
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found version "2.7.6") 
-- Found Cython: /home/travis/virtualenv/python2.7.14/bin/cython  

[marcogario]

@mikand maybe you are more familiar with cmake, and have an idea of how to fix this? It might be the case that we need to fix it upstream, but it is such a niche case, that I would rather work-around it in Travis or provide a patch to the boolector team.

[marcogario]

This seems to be a known issue. It mostly affects Mac users (due to the common usage of homebrew and other non-system versions of python). For us the easiest solution would be to call the cmake with the correct flags.

For Travis only, here is how another project solved it for linux.
SimonRit/RTK@689fa97

[mikand]

@marcogario Are you working on this? If you want I can try to fix the CI somehow...

[marcogario]

I reported this to the Boolector team to identify a principled solution. What I was trying (and you can take over) was to modify the cmakecache from within our installer.

[mikand]

The PR should be almost OK now, but tests are failing because it seems that CVC4 1.5 wrapper does not work on python 2.7 and swig3. My suggestion is to postpone the merge of this pr after #552 that should solve the issue with CVC4.

[mikand]

@marcogario This is ready to merge for me, can you have a look and (if ok) go ahead and merge?