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_path
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
ug
FWIW: nodejs error when it fails to load openssl errors is also a bit
confusing and needs OPENSSL_MODULES export:
https://lists.openembedded.org/g/openembedded-devel/message/96799
On Thu, Sep 15, 2022 at 1:26 PM Mikko Rapeli
wrote:
> Hi,
>
> On Thu, 15 Sept 2022 at 14:18, Ross Burton wrote:
> >
Hi,
On Thu, 15 Sept 2022 at 14:18, Ross Burton wrote:
>
> On 14 Sep 2022, at 09:09, Mikko Rapeli via lists.openembedded.org
> wrote:
> > Found the root cause. As suggested on #pyco too maybe native openssl
> > was mising legacy support.
> > It wasn't but loading the on purpose hidden openssl le
On 14 Sep 2022, at 09:09, Mikko Rapeli via lists.openembedded.org
wrote:
> Found the root cause. As suggested on #pyco too maybe native openssl
> was mising legacy support.
> It wasn't but loading the on purpose hidden openssl legacy.so was
> failing. It is located in
> recipe-sysroot-native/usr/
On Wed, 2022-09-14 at 11:09 +0300, Mikko Rapeli wrote:
> Hi,
>
> Found the root cause. As suggested on #pyco too maybe native openssl
> was mising legacy support.
> It wasn't but loading the on purpose hidden openssl legacy.so was
> failing. It is located in
> recipe-sysroot-native/usr/lib/ossl-mo
On Wed, 14 Sept 2022 at 10:51, Mikko Rapeli wrote:
> Was there some discussion in the past with openssl upstream about how
> to find config
> files, modules etc, or was there some alignment with e.g. Debian package?
I'm not aware of any such. Please open a ticket, and link to it in any
proposed o
On Wed, 14 Sept 2022 at 11:45, Alexander Kanavin wrote:
> But I'm not asking to make wrappers. I'm asking to patch openssl code
> itself to check for an oe-specific environment variable where it's
> making the decision where these things should be looked for. We
> already do this with native pytho
But I'm not asking to make wrappers. I'm asking to patch openssl code
itself to check for an oe-specific environment variable where it's
making the decision where these things should be looked for. We
already do this with native python.
Alex
On Wed, 14 Sept 2022 at 10:43, Mikko Rapeli wrote:
>
>
On Wed, 14 Sept 2022 at 11:19, Alexander Kanavin wrote:
> I can only think of patching openssl to pick up a oe-specific
> environment variable pointing to staging_libdir_native - making a
> wrapper for every native binary that sets those variables doesn't seem
> feasible.
Hmm. I'm a bit worried t
I can only think of patching openssl to pick up a oe-specific
environment variable pointing to staging_libdir_native - making a
wrapper for every native binary that sets those variables doesn't seem
feasible.
Alex
On Wed, 14 Sept 2022 at 10:09, Mikko Rapeli wrote:
>
> Hi,
>
> Found the root caus
Hi,
Found the root cause. As suggested on #pyco too maybe native openssl
was mising legacy support.
It wasn't but loading the on purpose hidden openssl legacy.so was
failing. It is located in
recipe-sysroot-native/usr/lib/ossl-modules/legacy.so and only found
via OPENSSL_MODULES
variable which was
On Tue, 2022-09-13 at 14:13 +0300, Mikko Rapeli wrote:
> On Tue, 13 Sept 2022 at 13:34, Richard Purdie
> wrote:
> > Are you using uninative? I'd have expected glibc and pthreads to come
> > from there rather than the host.
>
> Yes, using uninative, not host libc, sorry. Added full list of
> opena
On Tue, 13 Sept 2022 at 13:34, Richard Purdie
wrote:
> Are you using uninative? I'd have expected glibc and pthreads to come
> from there rather than the host.
Yes, using uninative, not host libc, sorry. Added full list of
openat()'d files to the end of this email, from master branch with
this pa
On Tue, 2022-09-13 at 13:29 +0300, Mikko Rapeli wrote:
> Hi,
>
> On Tue, 13 Sept 2022 at 13:01, Richard Purdie
> wrote:
> >
> > On Tue, 2022-09-13 at 12:34 +0300, Mikko Rapeli wrote:
> > > The python3-cryptography-native builds work but are functionally broken
> > > on Ubuntu 18.04 build host si
Hi,
On Tue, 13 Sept 2022 at 13:01, Richard Purdie
wrote:
>
> On Tue, 2022-09-13 at 12:34 +0300, Mikko Rapeli wrote:
> > The python3-cryptography-native builds work but are functionally broken
> > on Ubuntu 18.04 build host since the update from 3.3.2 in
> > meta-openembedded/meta-python. If recip
On Tue, 2022-09-13 at 12:34 +0300, Mikko Rapeli wrote:
> The python3-cryptography-native builds work but are functionally broken
> on Ubuntu 18.04 build host since the update from 3.3.2 in
> meta-openembedded/meta-python. If recipe needs and DEPENDS on
> python3-cryptography-native for signing use
The python3-cryptography-native builds work but are functionally broken
on Ubuntu 18.04 build host since the update from 3.3.2 in
meta-openembedded/meta-python. If recipe needs and DEPENDS on
python3-cryptography-native for signing use cases, loading
the python modules fails:
$ python3 -c "from O
18 matches
Mail list logo
