Closed loriab closed 8 years ago
Hmmm. That's indeed very odd. @wpoely86 : Do you have any idea?
Did you start from a clean build directory?
Yes, a fresh build directory within a well-used clone. And I hid pre-built libchemps
files that I thought it might detect. But I hadn't hidden the includes
dir that contained a 1.7
chemps2
headers dir because hdf5, etc. headers were also there. With that includes/chemps2
blown away, Psi4+CheMPS2-1.7.1 works fine, yay!
So Psi4+CheMPS2 is broken again with
1.7.1
. It seems to be down to theCASPT2::solve
function signature, which did change from1.7
: https://github.com/SebWouters/CheMPS2/compare/v1.7...v1.7.1 As shown below, when I do a psi4 build where CMake goes off and grabs the1.7.1
tag, compiles and installs it locally, then psi4 tries linking against the static, it complains about thesolve
sig, then when I fix it to add the default second arg, it complains anyway. Some preliminary facts:1.7.1
static --> FAIL1.7
static --> PASS1.7.1
dynamic --> PASS ( I checked the output, it has the 1.7.1 printing)Any ideas? @ryanmrichard, any reason a static library should be less able to handle signatures with default args? (here's the doxygen for you: http://sebwouters.github.io/CheMPS2/doxygen/classCheMPS2_1_1CASPT2.html#acda216c42c5245d79ae398ec59f2253f) I've looked at the link lines and I don't see anywhere an old 1.7 header could be lurking. I'm at a loss, so seeking ideas.
1 arg
existing code
compile fails in Internal build against
libchemps2.a
:two arguments in lib sig
2 arg
so I try to supply the second (supposedly default) arg
compile fails in Internal build against
libchemps2.a
:signature shows 2 args