The thing is that this is a bug on the Debian package. THEY have to fix it. Otherwise, we would end up with a code with plenty of #ifdef DEBIAN_CRYPTO-1 #ifdef DEBIAN_CRYPTO-2 ... ;-) In fact, the Debian crypto++ package, untill too weeks ago or so (maybe more) had another bug, but it's fixed now. Obviously the code can't be adapted to other's bugs, but other's bugs HAVE to be addapted to the correct way. ATM, all that can be done is to tell about the link that must be doen to anyone with the same problem on Debian... until the Debian Crypto++ mantainer fixes it.
I hope I made myself clear ;-)
Greetings.