Matt,
I tried using the following commad-line:
LD_LIBRARY_PATH=/usr/local/lib LIBPATH=/usr/local/lib ./jabberd/jabberd -D
since libssl and libcrypt live in /usr/local/lib. This did not work. I am
looking into compiling in some linker options into the binary so that it
has its library path set correctly at runtime.
--
Eli Ben-Shoshan [EMAIL PROTECTED]
Computer Programmer-Analyst
Northeast Regional Data Center VOX: (352) 392-2061
University of Florida FAX: (352) 392-9440
On Wed, 9 Oct 2002, matthew c. mead wrote:
> On Wed, Oct 09, 2002 at 03:53:50PM -0400, Eli Ben-Shoshan wrote:
> > Seems like ./pthsock/pthsock_client.so is not a valid library. I am not
> > sure why this is not a valid library since it does get compiled with the
> > openssl libraries. If I do not enable SSL then everything is okay. Anybody
> > have this problem or know how to fix it. Thanks.
>
> Is the openssl lib somewhere on your system? Is it in your
> LD_LIBRARY_PATH (or equivalent - I don't know AIX very well)? I
> had this issue under FreeBSD when my openssl library location was
> specified at build time for linking but when the library was loaded
> dynamically at runtime, the loader could not find the openssl
> library. FreeBSD uses a hints file that is generally built at boot
> time. If a library isn't in the hints file, the loader doesn't
> find it - hence my problem.
>
>
> -matt
>
> --
> matthew c. mead
>
> http://www.goof.com/~mmead/
> _______________________________________________
> jdev mailing list
> [EMAIL PROTECTED]
> http://mailman.jabber.org/listinfo/jdev
>
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
