Kaushalye Kapuruge wrote: > jimmy bahuleyan wrote: >> Kaushalye Kapuruge wrote: >> >>> Hi Listers, >>> I'm having a problem shipping my (xml security)library, which is based >>> on openssl crypto implementation. >>> I have statically linked it with the ssl and crypto libraries (-lssl >>> -lcrypto). >>> >> >> Are you sure you have statically linked in the Openssl libraries? If it >> was, then I don't think you'd get link errors for these symbols. >> >> I also believe all versions of 0.9.x to be binary compatible for the >> same 'x'. >> >> > Correction: It's not statically linked. :) My bad > But why I'm getting this error even if its dynamically linked, on > another machine with 0.9.8c? > What's the meaning of 0.9.8e in > "OpenSSL 0.9.8c 05 Sep 2006 (Library: OpenSSL 0.9.8e 23 Feb 2007)" > when I issue > %openssl version >
Well, if I understand things correctly here, that means your executable was built with 0.9.8c while the shared object available on the system is 0.9.8e. ($/openssl/apps/version.c). > What possible actions I can take to ship my library so that it'll work > on any 0.9.8x (rather than linking statically) ? > Thanks for the reply. :) > Cheers, > Kau As far as my knowledge goes if your build didn't do anything esoteric, then 0.9.8x libraries are binary compatible. Check if your executable has the proper dependencies and the openssl library installed is proper. Or maybe someone else can throw some light on this problem ;) -jb -- No snowflake in an avalanche ever feels responsible. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
