silviana amethyst

the more i think about your problem, the more i am becoming convinced that there are multiple versions of boost installed on your machine. the search for headers picked up...

i see the include path `-I/usr/include/include`in your attached `config.log` shows up when it's finding boost. Can you check if you have boost libraries at the location`/usr/include/lib`? that's my best guess....

you certainly could nuke it from orbit, but i don't think that in this instance, that's the only way to be safe. instead, let's work to educate you more fully...

another thing to try -- based on [this so post], consider removing `include` from the path you are passing to `--with-boost=`. that is, try `./configure --with-boost=/usr`? ultimately, we just need...

matching is good. where is that copy of `version.hpp`? are there multiple `version.hpp` files floating around? (in multiple `boost` folders?) can you find one with a different version number? are...

will you confirm that you have shared libraries at `/usr/lib/x86_linux_gnu`, please? do you have `libboost*` libraries with suffixes both `.so` and `.a`? this will help me understand whether it is...

also, thanks for sticking with this. i really appreciate it.

i think your problem in `ErrorAsOnCommandLine` might be out-of-memory. restrict the number of threads you are using, by `make -j 4`. or even 2. gcc is a memory hog for...

you're right about the error using `ldd`... the program `bertini2` isn't built by the current version of master. what if you `ldd .libs/libbertini2.0.so`? look for a major update to master...

pull and retry `make check`? remember, keep `-j #` low, to avoid OOM problems