On Tue, 2004-11-16 at 08:48 +0900, Carsten Haitzler wrote: > On Mon, 15 Nov 2004 18:12:51 -0500 Bart Elberg <[EMAIL PROTECTED]> babbled: > > > Looks like we have a similar problem and IT IS CRITICAL FOR US TO SOLVE > > THIS!! > > > > We're integrating our existing application libraries with an EFL-based > > GUI and once we start linking with libedb it core dumps. The trace looks > > like this: > > something else is pulling in a libdb (-ldb) link (another shared lib or an > explicit link). since edb is originally a fork of libdb2 (sleepycat's > libdb2.7) > with just a nice wrapper on top (due to libdb changing on-disk format every > minor version or 2 and thus making it impossible to open files created when > linked to a previous libdb) - it shares internal symbol names and this does > screw things up. the solution is more or less a lot of mind-numbingly boring > "sed" work with symbols in the code (also being careful to not be too zealous > and change something that is a substring of something else).
Another option which I throw out there is to update the libdb code in edb to using db-4.x (or something like 3.x). Basically atleast the min version that has --with-uniquename=option which makes the build of db use unique symbols for all its stuff. I use db-4.x in my libstldb4's internal db-4.x and it links into apps nicely which also link to other "standard" db libs. From rom looking at the edb source it appears to be a version of db from before they had the unique-name option. If we are updating edb's db it would be better to do it now than after a release. I am not sure how much bigger an edb with db-4.x will be as compared to its current form.
signature.asc
Description: This is a digitally signed message part
