On 25 March 2015 at 16:28, Mark Asselstine <mark.asselst...@windriver.com>
wrote:
> For target builds libdir is not something that changes and for -native
> builds unless you move your builds around you will see no issue with
> the current implementation. If you do update libdir or if you move
> your build or reuse sstate by copying it to a new build you will start
> to see errors. These will be seen when you use the 'openssl' tool and
> look like the following:
>
> WARNING: can't open config file: /home/build/bitbake_build/tmp/
> sysroots/x86_64-linux/usr/lib/ssl/openssl.cnf
>
We don't generally require that native sstate is rebuilt when the build
directory changes, as otherwise you wouldn'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 "fix" binaries. Indeed
openssl.inc does this:
do_install_append_virtclass-native() {
create_wrapper ${D}${bindir}/openssl \
OPENSSL_CONF=${libdir}/ssl/openssl.cnf \
SSL_CERT_DIR=${libdir}/ssl/certs \
SSL_CERT_FILE=${libdir}/ssl/cert.pem \
OPENSSL_ENGINES=${libdir}/ssl/engines
}
Is it possible that the binary isn't respecting the OPENSSL_CONF
environment variable since that wrapper was written? (or the wrapper wasn't
tested well enough)
Ross
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
