On 1/8/2013 2:43 PM, Serhiy Ivanov wrote:
Could you kindly explain how to explicitly point out to linker some library.
Line "-l /usr/local/ssl/lib/libssl.a" of course fails. At least -l is
not meant to point out explicit library.
Can i reconfigure my openssl library in that way that no ".so" output
will generated at all?
On Tue, Jan 8, 2013 at 2:36 PM, Jakob Bohm <jb-open...@wisemo.com> wrote:
On 1/8/2013 10:03 AM, Serhiy Ivanov wrote:
I built my simple project with -lssl option, so libsssl.a qattached
statically. However as i see from map report i see next pages:
The command
cc -lssl
tells the compiler and linker to look for either libssl.a or libssl.so along
its library search path.
If it finds libssl.so before finding libssl.a, libssl.so wins and libssl.a
is not used at all.
Try specifying /some/path/libssl.a explicitly just to test that this
is the issue, if it is not you will have to ask again.
If it is a matter of cc finding libssl.so first, you may be able to
use other command line options to change which directory it looks in
first. However if libssl.so and libssl.a are in the same directory,
or changing the order to get the directory with libssl.a first makes
something else not work, you will just have to specify the .a file
directly.
just pass the libssl.a file name as a normal argument (not as an
option). Most versions of cc will recognize the ".a" file extension
and do the right (or almost right) thing.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com
Transformervej 29, 2730 Herlev, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
