Hi!
> Well I remember that (at least gcc/ld) first .so are searched and then .a for
> a given -l. So if you only have libssl.a/libcrypto.a in the path then
> it should work.
>
> OR
>
> You could directly give libssl.a/libcrypto.a in the link command (not
> -lssl, -lcrypto).
>
> >
> > Also, sinc
On Jan 25, 2008 1:29 PM, Jimmy B <[EMAIL PROTECTED]> wrote:
> On Jan 23, 2008 7:17 PM, Bobby Krupczak <[EMAIL PROTECTED]> wrote:
> >
> > Hi!
> >
> > > > Static linking does not seem appropriate as I cant get my app to
> > > > statically link against libssl/libcrypto (I get lots of undefined
> > > >
On Jan 23, 2008 7:17 PM, Bobby Krupczak <[EMAIL PROTECTED]> wrote:
>
> Hi!
>
> > > Static linking does not seem appropriate as I cant get my app to
> > > statically link against libssl/libcrypto (I get lots of undefined
> > > symbol errors) and statically linking tends to not work well across
> > >
Hi!
> > Static linking does not seem appropriate as I cant get my app to
> > statically link against libssl/libcrypto (I get lots of undefined
> > symbol errors) and statically linking tends to not work well across
> > platforms that have different versions of underlying libraries.
> >
>
> That s
On 1/23/08, Bobby Krupczak <[EMAIL PROTECTED]> wrote:
> Hi!
> Static linking does not seem appropriate as I cant get my app to
> statically link against libssl/libcrypto (I get lots of undefined
> symbol errors) and statically linking tends to not work well across
> platforms that have different ve
