On Tue, 2022-09-20 at 13:20 +0300, Mikko Rapeli wrote: > Hi, > > I created an issue in openssl about this: > > https://github.com/openssl/openssl/issues/19242 > > Then I have the openssl patches in: > > https://github.com/openssl/openssl/compare/master...mikkorapeli-linaro:openssl:relative_paths > > The feedback so far is cold in upstream. Yes, the patches are a bit > ugly too, but IMO so are the original code paths in openssl. > I'll follow-up on openssl side if there is anything that could be > improved. Comments and more feedback is welcome. > > So what should we do now on oe side? python3-cryptography is > completely broken and users really need to export at least > > export OPENSSL_MODULES="${STAGING_LIBDIR_NATIVE}/ossl-modules" > > or apply > https://github.com/openssl/openssl/commit/a10a6c298878cf438cc8c13f5878d97f476eb0d0 > to openssl-native. > But that still leaves config files, engines and certificate paths broken.
Are there any other ways we could patch the code? Some ideas offhand are: a) the paths could be relative to the main library location? b) the paths could have a token in them with is replaced with the library path (a bit like $ORIGIN in RPATH)? That might be more acceptable to upstream and be a bit less invasive? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#170895): https://lists.openembedded.org/g/openembedded-core/message/170895 Mute This Topic: https://lists.openembedded.org/mt/93651845/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
