<div dir="auto"><div dir="auto">We are doing this for Linux. See below. Don't recall changing anything related to static build in transition from 1.0.2 to 1.1.1.</div><div dir="auto"><br></div><div dir="auto">For Windows we use the dlls. Noticed that new windows compile creates static libs, so we might convert to using the static libs.</div><div dir="auto"><br></div><div dir="auto">dev@turmeric:/NAS/dev/projectx/OPENSSL/bin/SUSE-Linux> ldd openssl</div><div dir="auto"><br></div><div dir="auto"> linux-vdso.so.1 (0x00007ffe023e4000)</div><div dir="auto"><br></div><div dir="auto"> libdl.so.2 => /lib64/libdl.so.2 (0x00007f551e24e000)</div><div dir="auto"><br></div><div dir="auto"> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f551e031000)</div><div dir="auto"><br></div><div dir="auto"> libc.so.6 => /lib64/libc.so.6 (0x00007f551dc8a000)</div><div dir="auto"><br></div><div dir="auto"> /lib64/ld-linux-x86-64.so.2 (0x00007f551e452000)</div><div dir="auto"><br></div><div dir="auto">dev@turmeric:/NAS/dev/projectx/OPENSSL/bin/SUSE-Linux> ./openssl version</div><div dir="auto"><br></div><div dir="auto">OpenSSL 1.1.1c 28 May 2019</div><div dir="auto"><br></div><br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Tue, Jul 23, 2019, 5:02 AM K Lengauer <<a href="mailto:kevin.lengauer@adnovum.ch">kevin.lengauer@adnovum.ch</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
I am trying to build the 'openssl' binary with libssl and libcrypto linked<br>
statically because the end product may be used on a system where they are<br>
not available. I recently upgraded to OpenSSL v1.1.1c and previously used<br>
1.0.2s which allowed me to get the 'openssl' binary with statically linked<br>
libssl and libcrypto.<br>
<br>
I went through several questions and boards already and tried different<br>
things:<br>
1) Using "no-shared" and "-static" for that matter with ./config is not an<br>
option as I still require the libcrypto.so and libssl.so for some other<br>
tests that are part of the whole component to which OpenSSL belongs in my<br>
use-case.<br>
2) My "solution" so far is to change the "<a href="http://build.info" rel="noreferrer noreferrer" target="_blank">build.info</a>" in /openssl/apps in<br>
the following way:<br>
<br>
source: DEPEND[openssl]=libapps.a ../libssl <br>
changed to: DEPEND[openssl]=libapps.a ../libssl.a ../libcrypto.a<br>
<br>
This way I am able to build both the openssl binary with statically linked<br>
libraries as well as keep building the shared libraries.<br>
<br>
However, here comes the catch. In doing so I break several of the OpenSSL<br>
unit tests (notably all 70-* recipe tests such as 70-test_comp.t, etc.) and<br>
they encounter a segmentation fault. I could provide a backtrace of the core<br>
for such a segfault.<br>
If I dont link the libraries statically and instead use the config to point<br>
it to the built .so files the tests run just fine.<br>
<br>
Is there a (better) way to achieve my goal to build the 'openssl' binary<br>
with statically linked libcrypto and libssl? I read in a recent question<br>
that statically linking is not recommended but still ask you kindly for any<br>
advice you can give me on this matter.<br>
<br>
I am sorry for this lengthy question but I tried to offer some insight in my<br>
thought process so far. Furhter, I apologize if my error is obvious as I am<br>
still learning the topics related to OpenSSL and especially the changes that<br>
occured since OpenSSL v1.1.0.<br>
<br>
<br>
<br>
<br>
<br>
<br>
--<br>
Sent from: <a href="http://openssl.6102.n7.nabble.com/OpenSSL-User-f3.html" rel="noreferrer noreferrer" target="_blank">http://openssl.6102.n7.nabble.com/OpenSSL-User-f3.html</a><br>
</blockquote></div></div>