From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.8.0.1) Gecko/20060202 Fedora/1.5.0.1-2 Firefox/1.5.0.1 Description of problem: gnucache links against libdb-4.1 if compat-db-4.2 is installed in the buildroot. It should try to link against the most current version first, then older ones. Version-Release number of selected component (if applicable): gnucash-1.8.12-3 How reproducible: Always Steps to Reproduce: 1. install compat-db-4.2 2. rebuild gnucash 3. compare package requirements with original package Actual Results: During configure: checking for __db185_open in -ldb-3... no checking for __db185_open in -ldb-4.0... no checking for __db185_open in -ldb-4.1... yes (This check doesn't fail because db4/db.h is valid for db-4.1, too) --- gnucash-1.8.12-3.x86_64.rpm 2006-02-22 11:27:36.000000000 +0100 +++ ../everything/gnucash-1.8.12-3.x86_64.rpm 2006-02-22 11:26:27.000000000 +0100 @@ -13,7 +13,7 @@ libc.so.6(GLIBC_2.3.4)(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) -libdb-4.3.so()(64bit) +libdb-4.1.so()(64bit) libdl.so.2()(64bit) libdl.so.2(GLIBC_2.2.5)(64bit) libesd.so.0()(64bit) Expected Results: no difference in package requirements Additional info: the configure script is checking for db-3, then db-4.0, db-4.1, db-4.2 and then db. This order should be reversed to link against the newest db found in the buildroot.
Hm, I may just look at fixing this upstream as it doesn't affect our built packages ATM.
This should be fixed in 1.9.x.