[bug-notifications] [ap2_modperl 0004749]: ap2_modperl from "current" requires BDB 4.7 and 4.8, fails to link to 4.7

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4749 
====================================================================== 
Reported By:                LFMM
Assigned To:                
====================================================================== 
Project:                    ap2_modperl
Issue ID:                   4749
Category:                   packaging
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2011-04-08 15:08 CEST
Last Modified:              2011-04-13 10:47 CEST
====================================================================== 
Summary:                    ap2_modperl from "current" requires BDB 4.7 and 4.8,
fails to link to 4.7
Description: 
Hello, world.

I cannot use ap2_modperl directly because it fails to link to libdb-4.7
(but it IS installed!!). See ldd output in "additional information".

A symlink to /opt/csw/bdb47/lib/libdb-4.7.so under /opt/csw/lib solves the
issue, but I'm not happy about the linking status afterwards (it uses both
BDB 4.7 and 4.8).

For my own education, where does the "misterious" dependency on 4.8 come
from? It's not listed in the "dump" output. Also, the RPATH doesn't make
much sense to me (refers to BDB 4.4, but NEEDS specifies 4.7). Finally,
"current" pkgutil introduces BDB 4.8, can mod_perl be rebuilt against it
and get rid of 4.7?

Thanks.
====================================================================== 

---------------------------------------------------------------------- 
 (0008958) LFMM (reporter) - 2011-04-13 10:47
 https://www.opencsw.org/mantis/view.php?id=4749#c8958 
---------------------------------------------------------------------- 
Rebuilding the package from the GAR HEAD but in a cleaner environment
solves all problems.