"fatal error: db_cxx.h: No such file or directory"

[curmudgeon]

I just installed sys-libs/db-4.8.30 (having run this system without db for a while).

I am having a problem building other (non-gentoo) apps.

I keep getting messages like "fatal error: db_cxx.h: No such file or directory"

I seems this can be solved by either exporting BDB_INCLUDE_PATH=/usr/include/db4.8/ or linking /usr/include/db4.8/db_cxx.h to /usr/include/db_cxx.h.

That leads me to a couple of questions.

First, shouldn't the db ebuild be doing one of those on installation?

Second, is one method preferred over the other (and why)?

[VoidMage]

Probably the first one, as long as you're exporting only during build time.
The problem here is that while sys-libs/db is slotted, due to various reasons (many going back to times where slotting was far less common), it's done in a very crude way, mainly due to issues specific for this package (like databases generated by the lib being incompatible between versions).
Ebuilds using this package tend to have special fixes for this slotting. Actually, those that don't are even more annoying from maintainer's point of view, as they tend to have a random selection of the versions, they check for. That's one of the reasons why >=5.0 slots are still masked, years since release and getting a masked ebuild into the tree.