Hi,
app-crypt/heimdal looks for db header files in db4/db.h db3/db.h db.h
db_185.h - in that order - and links with ldb. In Gentoo, we do not
have a db4 directory but rather db3 db4.7 db4.8 db5.0 etc.
Consequently, when both sys-libs/db-3 and sys-libs/db-4 are present,
heimdal links against libdb, which is a symlink against libdb-4.x, but
uses headers from db-3. Result is a segfault in heimdal - serves it
right for mixing it up :) .
* I am guessing this is not the first time. Any pointers on how to
solve this gracefully? inheriting db-use in ebuild and sedding works but
- is ugly
- there is a bunch of #ifdef db4/db.h's in the source so sedding the
configure script is not enough
- this is a security related package so I try to refrain from patching
* I can submit upstream a proper patch that will make the code look at
db.h first and db4/db.h db3/db.h later. Is there a (unwritten?) rule
that says look at db.h first? Any links?
* All linuxes I checked work correctly if the code looks at db.h first.
What's the case in *BSD, Solaris, etc? Is Linux a special case in
this regard?
Thanks
--
Eray
