Hi Jayjwa,
   
  Thank you very much! I followed your analysis and answers and solved the problem. Thanks again.
   
  Gary
   
   
>Name: OpenSSL
>Description: Secure Sockets Layer and cryptography libraries and tools
>Version: 0.9.8g
>Requires:
>Libs: -L${libdir} -lssl -lcrypto -ldl
>Cflags: -I${includedir}
>My guess is a botched Openssl install and/or possibly something throwing off
>the linker. libcrypto.so should be linked with libdl on Linux as far as I can
>tell.
>Also, as specified, it's doubtful the cc or cpp would have found the Openssl
>includes in /usr/local/ssl/include/openssl/* (I saw no
>-I/usr/local/ssl/include). Openssl is a main component, and is usually
>prefixxed at /usr, or bad/weird things happen (I'm wondering what your
>PKG_CONFIG_PATH is set to if Openssl is making its own teir under local/). I'd
>rebuild it, but you might be able to work around it by holding the
>compiler & linker's hand and specifically setting PKG_CONFIG_PATH to include
>wherever openssl.pc landed at, CFLAGS/CPPFLAGS to -I/usr/local/ssl/include,
>LDFLAGS to -L/usr/local/ssl/lib, and linking in -ldl with anything that
>is using ssl libs from now on. You'll also need to tell the dynamic linker
>where libcryto.so/libssl.so are (ld.so.cache, rpath, LD_*) if linking
>dynamically, or make sure the *.a static versions are compiled in statically.
   
   

 __________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Received on 2007-11-03