On Thu, Jul 02, 2015 at 07:11:30PM +0530, Kartik Mistry wrote: > CC'ng libxapian maintainer in case it is fixed there and we can upload fix.
The ABI check in the xapian-core headers dates back to the GCC 3.x days when the ABI changed more than once and if you mixed objects you'd end up with a linker error which didn't give you any obvious clue that the issue was a mixture of C++ ABIs. Rather than have to respond to repeated user reports of such problems (and know that there were undoubtedly even more people hitting this and giving up in frustration) we added this check. GCC 3.4 to 4.9.x inclusive default to ABI v2 (but slowly added newer versions you could explicitly select); GCC 5 defaults to ABI v8. So this error is right to say the ABI has changed incompatibly, but these ABI changes apparently only affect obscure cases, so in practice it'll probably work - I tried xapian-core built with GCC 4.9 and xapian-bindings built with GCC 5 and the bindings testsuites all pass. Xapian-core 1.2.21 relaxes this ABI mismatch error to a warning when both the ABI versions are >= v2. I uploaded 1.2.21-1 to unstable on 2015-05-21 so I'd expect recoll will build with just a warning in this case now. Even if not, doko's planning a mass rebuild of everything with GCC5 anyway, and if you use the same compiler version there's no C++ ABI mismatch: https://release.debian.org/transitions/html/libstdc++6.html Cheers, Olly -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
