Re: full static linkage

2013-01-08 Thread Serhiy Ivanov
Let's close question with full path for library (simply no -l option need). On Tue, Jan 8, 2013 at 2:36 PM, Jakob Bohm 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 s

Re: full static linkage

2013-01-08 Thread Jakob Bohm
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" out

Re: full static linkage

2013-01-08 Thread Serhiy Ivanov
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, 2

Re: full static linkage

2013-01-08 Thread Jakob Bohm
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 pa