Thanks for your help. I tried to compile the testprogram with "gcc ssl_accept.c 
-o sslaccept -lssl -lcrypto -L/usr/lib"
When executing ./sslaccept I get ./sslaccept: error while loading shared 
libraries: /usr/lib/libcrypto.so.1.0.0: undefined symbol: H, version 
efault_method

The shared libarieĀ /usr/lib/libcrypto.so.1.0.0 exists. Something other may be 
broken?

The sslaccept test programm will be executed when I use ./configure to compile 
some software which is testing if openssl is installed. So I'm not able to 
change the source of sslaccept.

greetings

----------------------------------------
> From: [email protected]
> To: [email protected]
> Date: Thu, 4 Apr 2013 05:46:03 -0600
> Subject: RE: testprogram results in undefined reference to x
>
> Wow, that's a lot of output :)
>
> First of all, you need -lssl and -lcrypto. Where did you install the OpenSSL 
> libraries, are they in a common place that your compiler can find? If not, 
> you'll need to add -L/xxxx where xxxx is the path to the place where the 
> libraries (libssl.a for example) can be found.
>
> >/* Override any GCC internal prototype to avoid an error.
> > Use char because int might match the return type of a GCC
> > builtin and then its argument prototype would still apply. */
> > #ifdef __cplusplus
> > extern "C"
> > #endif
> > char SSL_accept ();
>
> Interesting and well-meaning, but wrong. The right thing to do is
> #include "openssl/ssl.h"
> And you might need to add -I flags on your compile line.
>
> /r$
>
> --
> Principal Security Engineer
> Akamai Technology
> Cambridge, MA
>
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> User Support Mailing List [email protected]
> Automated List Manager [email protected]                                  
>   ______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [email protected]
Automated List Manager                           [email protected]

Reply via email to