Hi Nicholas,
your 2.3.2 executable is statically linked and doesn't require those
shared libraries to be available on your system.
During the the 2.3.3 life-cycle it became apparent that static linking
on Unix is incompatible with a few low-level functions GnuGk is using
(eg. dlopen()) and can cause hard crashes, thus the 2.3.4 executables
are dynamically linked.
Most probably you have libssl on your system, usually in /usr/lib/, but
probably a slightly different version. You can just make a symbolic
link, eg. ("ln -s libssl.so.0.9.7.so libssl.so.0.9.8.so").
Regards,
Jan
Nicholas Thompson wrote:
> Hello,
>
> I am currently running the pre-compiled 2.3.2 (32bit) on Centos 5.5 without
> any problems. However, I downloaded the 2.3.4 executable (32bit) and this
> is what I get when I run the command:
>
> error while loading shared libraries: libssl.so.0.9.8: cannot open shared
> object file: No such file or directory
>
>
> I know CentOS uses OpenSSL, not libssl. What changed between 2.3.2 and
> 2.3.4 and how do I fix it?
>
> Thanks!
> Nick~
--
Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/
------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web. Learn how to
best implement a security strategy that keeps consumers' information secure
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________________
Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx
Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users
Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users
Homepage: http://www.gnugk.org/
