Thanks for the reply Mike.
> dont link static libraries into shared libraries and it isnt a problem
Ya that is true. But, I do want to link the static library to the shared
library.
> pic adds a lot of overhead with x86 due to register pressure
Can you point me to link or something that discusses this in more detail?
Thanks again for the help.
--- On Tue, 11/3/09, Mike Frysinger <vapier....@gmail.com> wrote:
> From: Mike Frysinger <vapier....@gmail.com>
> Subject: Re: Static libraries with fPIC on 32bit system
> To: openssl-users@openssl.org
> Date: Tuesday, November 3, 2009, 1:41 PM
> On Mon, Nov 2, 2009 at 21:37, john
> blair wrote:
> > I have built openssl-0.9.8k and am trying to link
> libcrypto.a statically with my project. I think libcrypto.a
> contains contains non-relocatable functions
> > For example, consider the following:
> > #include <openssl/des.h>
> > void foo(void) {
> > DES_encrypt3(NULL, NULL, NULL,
> NULL);
> > AES_encrypt(NULL, NULL);
> > }
> >
> > $ gcc -fPIC -o libfoo.so -shared foo.c
> /usr/lib/libcrypto.a
>
> dont link static libraries into shared libraries and it
> isnt a problem
>
> > Can someone point me to why building static libs on 32
> bit system with fPIC is a bad idea?
>
> pic adds a lot of overhead with x86 due to register
> pressure
> -mike
> ______________________________________________________________________
> OpenSSL Project
>
> http://www.openssl.org
> User Support Mailing List
> openssl-users@openssl.org
> Automated List Manager
>
> majord...@openssl.org
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
