I wouldn't have discovered this issue if my build system library was
'libdb-4.0' because the FC5 system uses libdb-4.3 and my library would
have been loaded. This is most likely a special case where both the
build and test systems use 'libdb-4.3', but the perl module,
'DB_File.so' checks the major, minor, and patch version numbers against
the loaded lib and if they don't match I get a compatibility error.
-paul
Chris Dolan wrote:
On Dec 7, 2006, at 12:10 PM, Paul Salazar wrote:
I looked into this further and found that the 'libdb' extracted to
the temp dir will get loaded properly IF the FC5 system 'libdb' is
not found. So it is getting picked up by the 'LD_LIBRARY_PATH' env,
but ONLY if the system lib is missing. How can I get the
LD_LIBRARY_PATH env to be the FIRST place the loader looks for shared
libs?
cheers,
Paul
I have not had to deal with that scenario myself. My production
platforms are pretty predictable (Mac 10.4 and Windows XP) so I've
always either used the system library, or I have known that my library
will be the only copy.
Chris
--
Chris Dolan, Software Developer, Clotho Advanced Media Inc.
608-294-7900, fax 294-7025, 1435 E Main St, Madison WI 53703
vCard: http://www.chrisdolan.net/ChrisDolan.vcf
Clotho Advanced Media, Inc. - Creators of MediaLandscape Software
(http://www.media-landscape.com/) and partners in the revolutionary
Croquet project (http://www.opencroquet.org/)
