On 11/29/2009 08:17 PM, Pete Zaitcev wrote:
Fedora 13 comes with db4.8 and apparently the compat-db4.7 is bust.
Let us link with 4.8 as a workaround.
Signed-Off-By: Pete Zaitcev<zaitcev@xxxxxxxxxx>
---
configure.ac | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
Not sure how safe or desirable this is, but it seems to work.
commit 77e89dfc8f0a9296ebfb02d5ca34d48f083df50c
Author: Master<zaitcev@xxxxxxxxxxxxxxxxxxx>
Date: Sun Nov 29 18:12:40 2009 -0700
Fix crash in __mutex_get_max because db4.7 is toast on F13
by letting to link against db4.8.
Interesting... I recall the root cause clearly, now: /usr/include/db.h
always refers to the latest installed db4, even if compat-db{,45,46} is
installed. Our configure recipe links with the most recent db4 listed
in configure.ac, combined with the installed /usr/include/db.h. Thus,
each new db4 version produces a mismatch.
If we could include /usr/include/db4.6.21/db.h when db-4.6 is present,
that would be ideal. But given that db4 lacks anything approaching
pkgconfig, autodetection becomes quite difficult.
While I would like to see configure.ac have a better test (surely Google
can find an autoconf recipe for db4?), I think your proposed patch will
be the best method we can find.
Jeff
--
To unsubscribe from this list: send the line "unsubscribe hail-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
