...
Since However since library is only provided as binary and not as source to sources we cannot see how build recipes bring in wrong linking, dependencies and we as RDK-M cannot investigate (access requires ARM approval Mali DDK license) we and RDK-M cannot investigate and action is fully on amlogic. However Amlogic no longer provides support for this!
TO DO insert REFERENCE TO AML Jira TICKET TO INVESTIGATE / FIX this
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
"deps": [
"/lib/ld-linux-armhf.so.3",
"/lib/libc.so.6",
"/lib/libdl.so.2",
"/lib/libgcc_s.so.1",
"/lib/libm.so.6",
"/lib/libpthread.so.0",
"/lib/librt.so.1",
"/usr/lib/libdrm.so.2",
"/usr/lib/libstdc++.so.6",
"/usr/lib/libwayland-client.so.0",
"/usr/lib/libwayland-server.so.0"
],
"name": "/usr/lib/libMali.so" |
on broadcom it is ok since move to newer brcm wayland backend in RDK6 no issue(WLPL) in RDK6
libs deps https://github.com/stagingrdkm/lgpub/blob/master/dac/templates/oe_4.0/72126ott_libs.json
issue to be described
Same problem as amlogic
Since library is only provided as binary and not to sources we cannot see how build recipes bring in wrong linking, dependencies and we as RDK-M cannot investigate.
libs deps https://github.com/stagingrdkm/lgpub/blob/master/dac/templates/oe_4.0/rtd1319_libs.json
...