> From: owner-openssl-us...@openssl.org On Behalf Of Eystein Måløy Stenberg > Sent: Monday, 21 September, 2009 02:59
> You nailed it. > "gcc -I/usr/local/ssl/include -L/usr/local/ssl/lib aes.c -lcrypto" > works perfectly. > However, on Red Hat, it compiles and links no matter where I > put the input file (checked it again). > On Mon, Sep 21, 2009 at 12:30 AM, Dave Thompson > <dave.thomp...@princetonpayments.com> wrote: > > The 'gcc' linker (ld) (and AFAIK most others) is order sensitive. > > You must have -lcrypto *after* the module(s) that calls it. <snip> On further checking, I realized it's different for static versus dynamic/shared linking; the latter works anywhere (even first). You apparently got dynamic built-in on Linux, but static in your own build. Sorry for being partly off. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
