Not that I'm aware of (not that that means anything). And I'm hard-pressed to conjure up something that isn't already covered in the application documentation. Also, I think there's enough to take in already without adding edge-case technical administrivia. This particular example is constrained to a specific userland area - that of casual appeal to the community for assistance with trivial issues of compilation instead of RTFM, where the instructions are copy'n'pasta-ready:

https://github.com/nochowderforyou/clams/blob/master/doc/build-unix.md#berkeley-db

If the official docs are unread, that's just as likely to apply to any centralised resource.

Anyway, the issue of binary compatibility of wallet.db is only really an issue for distributors of proprietary OS applications (OS X and Windows - Linux users are free to choose which libraries are linked to) and, strictly speaking (this is cryptocurrency), the provision of binaries introduces security issues. Reflecting this, there is a supported/ing build system (https://github.com/nochowderforyou/clams/blob/master/doc/gitian-building.md) which is deterministic i.e. a hash of the resulting code binaries (Linux, OS X, Windows, depending on selection) will always be the same, so it can be cross-referenced against the published hash. All very open and verifiable.

Cheers

Graham