126 replies to this topic

[rantanplan]

Build with symlink libcrypt was allways defined here

https://github.com/O...o-compat_1.1.bb

Simply install it and test locally whether something has changed.
I do not think so. We are using the more recent version than OE

[A.A.]

just installing lybcrypto-compat does not help.

 

I will try like in OE-A:

 

andrea@andrea-ThinkPad-T520:/oe/oe-alliance/meta-oe-alliance$ grep -R PREFERRED_ . | grep ssl
./meta-oe/conf/layer.conf:PREFERRED_PROVIDER_openssl = "openssl10"
./meta-oe/conf/layer.conf:PREFERRED_PROVIDER_libcrypto = "openssl10"
./meta-oe/conf/layer.conf:PREFERRED_PROVIDER_libssl = "openssl10"
./meta-oe/conf/layer.conf:PREFERRED_PROVIDER_openssl-native = "openssl10-native"
./meta-oe/conf/layer.conf:PREFERRED_PROVIDER_libcrypto-native = "openssl10-native"
./meta-oe/conf/layer.conf:PREFERRED_PROVIDER_libssl-native = "openssl10-native"
andrea@andrea-ThinkPad-T520:/oe/oe-alliance/meta-oe-alliance$

 

EDIT:

OpenPLi is the same...?

 

andrea@andrea-ThinkPad-T520:/oe/oe-alliance/meta-oe-alliance$
R PREFERRED_ . | grep ssl20:/oe/openpli-oe-core/meta-openpli/conf/distrogrep -R
./openpli-common.conf:PREFERRED_PROVIDER_openssl = "openssl10"
./openpli-common.conf:PREFERRED_PROVIDER_libcrypto = "openssl10"
./openpli-common.conf:PREFERRED_PROVIDER_libssl = "openssl10"
./openpli-common.conf:PREFERRED_PROVIDER_openssl-native = "openssl10-native"
./openpli-common.conf:PREFERRED_PROVIDER_libcrypto-native = "openssl10-native"
./openpli-common.conf:PREFERRED_PROVIDER_libssl-native = "openssl10-native"

You know what I'll do, remove 1.1 and rebuild all.

Will take some time

A.A.

Edited by A.A., 3 May 2021 - 13:10.

[rantanplan]

mhh ...
but there are no build errors in this regard.
What are you hoping for?
Is it still about the sound?
For me, the only difference is the activation of PulseAudio.

[A.A.]

By happy chance downgrading to openssl1.0 did not resolve.

And if the guys at OE-A have a branch named nextp3-ssl111 it means the problem is elsewhere.

 

Next I'll verify autofs and nfsserver settings

[betacentauri]

That there is a branch nextp3-ssl111 don't prove that everything is working in this branch

[A.A.]

argh

 

I tried to get in touch with 'captain' to ask him what was the showstopper retarding kodi_18 on mipsel by them.

No answer so I built myself one OE-A distro, OpenSPA, which seems to be up-to-date about kodi.

In fact OE-A uses now SPA's kodiext.

 

For me at the moment enigma2 is not the problem, I verified that on homebuilt OpenSPA there aren't the vuplus extra drivers in my PR here:

https://github.com/v...-vuplus/pull/93

 

So I am confident it is just the environment.

The toolchain is (apparently) already checked.

 

The main problem is that kodi itself is big like an operating system and that I really don't know anything about its internals.

I can just fix its build...takes 20-30 mins each time...

 

cheers

A.A.

[WanWizard]

I wish I had your energy...

[A.A.]

@WanWizard

 

so the OpenSPA kodi binary does start on OpenPLi-ssl.1.0.

 

Now I'll try OpenPLi-ssl1.0 kodi on OpenSPA and see...

 

I don't want to believe it's the different toolchain/binutils flawed just for this single prog.

Ok, this is not helloword.c. more an OS

[A.A.]

Attached is OpenPLi's  kodi_18 log (own recipe built within OE-A 4.4/OpenSPA with minor changes) running in OpenPLi-dev-ssl1.0:

 

In dmesg last lines after starting kodi are:

...

[VID]: VIDEO_GET_SIZE aspect: 1 0
bcm7424: hotplug_callback():
Hotplug - status.connected 1:1:2
root@vuduo2:~#

 

Attached Files

•  kodi.log   13.14KB   7 downloads

Edited by A.A., 5 May 2021 - 21:29.

[A.A.]

And here how gdb sees the suxxer:

 

root@vuduo2:~# gdb /usr/lib/kodi/kodi-stb
GNU gdb (GDB) 8.3.1
Copyright © 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "mipsel-oe-linux".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/s...are/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/s...ocumentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/kodi/kodi-stb...
(No debugging symbols found in /usr/lib/kodi/kodi-stb)
(gdb) run
Starting program: /usr/lib/kodi/kodi-stb
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0x755f0410 (LWP 11705)]
[New Thread 0x74bff410 (LWP 11706)]
[New Thread 0x743fe410 (LWP 11707)]
[New Thread 0x73bfd410 (LWP 11708)]
[New Thread 0x731ff410 (LWP 11709)]
+GLES_Native_Init[127]
/tmp/dw.info read.. [1920x1080][9]
-GLES_Native_Init[139]
+GLES_Native_CreateNativeDisplay[144]
XBMC Display Resolution : 1920x1080, Stratch : 1
[New Thread 0x727ff410 (LWP 11711)]
[New Thread 0x628b4410 (LWP 11712)]
[New Thread 0x620b3410 (LWP 11713)]
[New Thread 0x618b2410 (LWP 11714)]
[New Thread 0x610b1410 (LWP 11715)]
-GLES_Native_CreateNativeDisplay[155]
+GLES_Native_CreateNativeWindow[161]
-GLES_Native_CreateNativeWindow[170]
[New Thread 0x608b0410 (LWP 11716)]
[New Thread 0x5feaf410 (LWP 11722)]
[New Thread 0x5f0ff410 (LWP 11725)]
[New Thread 0x5e8fe410 (LWP 11726)]
[New Thread 0x5e0fd410 (LWP 11727)]
[New Thread 0x5d8fc410 (LWP 11728)]
[New Thread 0x5d0fb410 (LWP 11729)]
[New Thread 0x5c6ff410 (LWP 11730)]
[New Thread 0x5befe410 (LWP 11731)]
[New Thread 0x5b6fd410 (LWP 11732)]
[New Thread 0x5aefc410 (LWP 11733)]
[New Thread 0x5a6fb410 (LWP 11734)]
[New Thread 0x59efa410 (LWP 11736)]
[Detaching after vfork from child process 11740]

 

[A.A.]

I wish I had your energy...

For me OE is an hobby but this one is now a personal matter

I only have a few weeks time  then real work will call again (hopefully)

 

Edit:

don't worry, we'll catch it at the end

Edited by A.A., 5 May 2021 - 22:12.

[A.A.]

Comparing the ldd output I see (again) only one diff at runtime: the binary built in OpenPLi needs

 

libfmt.so.6 => /usr/lib/libfmt.so.6

 

The one in OpenSPA does not need it at runtime.

[A.A.]

I see now, OE-A did alter the packaging and ships libfmt.a

[A.A.]

@WanWizard

 

the mips toolchain lacks "--with-mips-plt".

Vuplus modules probably have been compiled like this.

 

I am adding  "mplt" to DISTRO_FEATURES (like OE-A).

 

It was well hidden at the end of the log lines....

Rebuilding all, still with openssl10 for the moment.

 

A.A.

Edited by A.A., 7 May 2021 - 08:16.

[A.A.]

yes, it was just this...

[WanWizard]

Seen it. Already started recompiling, this will take a few days, the way it is going...

[rantanplan]

uih....
That means a lot of work for the build server.
All completely new build including gcc glibc.

The distro feature could possibly also have been added to Kodi bb or Kodi.inc.
Then the effort would be a little less.
But I'm sure too late

[WanWizard]

Yup, first image rebuild (dm8000) took 1 hour 38 min. Others should be faster, as the shared mipsel feed will not be rebuild.

[rantanplan]

Has the image size of the dm8000 changed anything?

[rantanplan]

Ok my build is even smaller
Then that's perfect.