Closed magnetophon closed 6 years ago
Hi, it's not exactly that your version is too new. This is my system:
$ xmllint --version xmllint: using libxml version 20904
And Beast checks for 20901. The problem is in the path you're using, our comparison macro picks up the "version" digits from the absolute pathname of your xmllint, and those won't match. In any case, your xmllint is new enough, so you can hack the configure script to ignore the version check, I'll see if our macro can be made more robust for cases like yours.
My version of libxml2 is too new:
Does the code really need this specific version, or can the check be changed to a "newer than" check?