Andreas Almroth wrote:
As it is Solaris, use export LD_OPTIONS='-R/usr/local/openssl-0.9.7g/lib
-L/usr/local/openssl-0.9.7g/lib'
The linker will take that into consideration, and if you do a dump -Lv
on the output file, the RUNPATH should be included.
I confirm that that fix is perfect for me.
Andreas Almroth wrote:
> As it is Solaris, use export LD_OPTIONS='-R/usr/local/openssl-0.9.7g/lib
> -L/usr/local/openssl-0.9.7g/lib'
> The linker will take that into consideration, and if you do a dump -Lv
> on the output file, the RUNPATH should be included.
*smacks head*
Ok, I wonder how I manag
Laurent Blume wrote:
prakash babu wrote:
*Solution 1 :*
Create a symbolic link in the system directory for libcrypto.so and
libssl.so
ln -s /usr/local/openssl-0.9.7g/lib/libcrypto.so /usr/lib/libcrypto.so
ln -s /usr/local/openssl-0.9.7g/lib/libssl.so /usr/lib/libssl.so
Evil. This is a sur
prakash babu wrote:
*Solution 1 :*
Create a symbolic link in the system directory for libcrypto.so and
libssl.so
ln -s /usr/local/openssl-0.9.7g/lib/libcrypto.so /usr/lib/libcrypto.so
ln -s /usr/local/openssl-0.9.7g/lib/libssl.so /usr/lib/libssl.so
Evil. This is a sure road to troubles at som
Hi,
I would suggest you two solutions
Solution 1 :
Create a symbolic link in the system directory for libcrypto.so and libssl.so
ln -s /usr/local/openssl-0.9.7g/lib/libcrypto.so /usr/lib/libcrypto.soln -s /usr/local/openssl-0.9.7g/lib/libssl.so /usr/lib/libssl.so
Solution 2
Specify a embedde
