<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 25 March 2015 at 16:28, Mark Asselstine <span dir="ltr">&lt;<a href="mailto:mark.asselstine@windriver.com" target="_blank">mark.asselstine@windriver.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id=":e1" class="" style="overflow:hidden">For target builds libdir is not something that changes and for -native<br>
builds unless you move your builds around you will see no issue with<br>
the current implementation. If you do update libdir or if you move<br>
your build or reuse sstate by copying it to a new build you will start<br>
to see errors. These will be seen when you use the &#39;openssl&#39; tool and<br>
look like the following:<br>
<br>
WARNING: can&#39;t open config file: /home/build/bitbake_build/tmp/<br>
                        sysroots/x86_64-linux/usr/lib/ssl/openssl.cnf</div></blockquote></div><div class="gmail_extra"><br></div>We don&#39;t generally require that native sstate is rebuilt when the build directory changes, as otherwise you wouldn&#39;t be able to share native sstate between builds and users.  Instead, paths are munged where possible when using sstate and wrapper scripts used to &quot;fix&quot; binaries.  Indeed openssl.inc does this:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">do_install_append_virtclass-native() {</div><div class="gmail_extra">        create_wrapper ${D}${bindir}/openssl \</div><div class="gmail_extra">            OPENSSL_CONF=${libdir}/ssl/openssl.cnf \</div><div class="gmail_extra">            SSL_CERT_DIR=${libdir}/ssl/certs \</div><div class="gmail_extra">            SSL_CERT_FILE=${libdir}/ssl/cert.pem \</div><div class="gmail_extra">            OPENSSL_ENGINES=${libdir}/ssl/engines</div><div class="gmail_extra">}</div><div class="gmail_extra"><br></div><div class="gmail_extra">Is it possible that the binary isn&#39;t respecting the OPENSSL_CONF environment variable since that wrapper was written? (or the wrapper wasn&#39;t tested well enough)</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div></div>