It doesn't make any difference in this case, but you'd be best to get in the
habit of putting the libraries last; for example
gcc cli.c -lssl -lcrypto
A few compilers only search libraries for references which they know about at
the time the library is listed. If you were using that sort of compiler, you
would still have your problem.
________________________________
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of xabi esteban
Sent: Sunday, February 28, 2010 11:27 AM
To: openssl-users@openssl.org
Subject: RE: Error copiling ssl: undefined reference
A lot of thanks, now roks perfectly.
The problem it was that i put the commnad line with -o and the correct
form was:
gcc -lssl -lcrypto cli.c
Thanks.
> Date: Sat, 27 Feb 2010 11:33:31 -0800
> From: pie...@hogranch.com
> To: openssl-users@openssl.org
> Subject: Re: Error copiling ssl: undefined reference
>
> xabi esteban wrote:
> > A lot of thanks but I'm vey confused and my english is not good. I
> > compile with ggc -o and you said that this is not enought, i need
> > linket too?
> > Put you put an example linking the libreres with gcc or example for
a
> > makefile? Thanks
>
> at a minimum, try adding -lssl -lcrypto to that gcc command line.
> this tells it to tell the linker phase to include libssl.so and
> libcrypto.so
>
>
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> User Support Mailing List openssl-users@openssl.org
> Automated List Manager majord...@openssl.org
________________________________
¡Nuevo MSN Entretenimiento! Todos los trailers, series de tv y
videoclips, los mejores juegos online y lo último sobre tus estrellas
favoritas. <http://entretenimiento.es.msn.com/>
