From: Markus Volk <f_l_k@t-online.de>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: widevine + arm64
Date: Fri, 19 May 2023 17:54:54 +0200 [thread overview]
Message-ID: <IJXWUR.OUXJ6LSOIO482@t-online.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Finally there's a libwidevinecdm.so achievable for arm64. To make it
usable by chromium/kodi it is required to patch glibc:
From 85892fbc0d6f64f564f0d4c9514a7183ad8eb985 Mon Sep 17 00:00:00 2001
From: alex <knaerzche@gmail.com>
Date: Sun, 17 Jul 2022 12:16:20 +0200
Subject: [PATCH] HACK: Don't check GLIBC_ABI_DT_RELR support for
ChromeOS
libwidevinecdm.so
Required starting with glibc 2.36
---
elf/dl-version.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/elf/dl-version.c b/elf/dl-version.c
index cda0889209..058394f148 100644
--- a/elf/dl-version.c
+++ b/elf/dl-version.c
@@ -373,7 +373,8 @@ _dl_check_map_versions (struct link_map *map, int
verbose, int trace_mode)
if (d->d_tag == DT_NEEDED)
{
const char *name = strtab + d->d_un.d_val;
- if (strncmp (name, "libc.so.", 8) == 0)
+ if (strncmp (name, "libc.so.", 8) == 0 &&
+ strstr (map->l_name, "libwidevinecdm.so") == NULL)
{
_dl_exception_create
(&exception, DSO_FILENAME (map->l_name),
--
2.37.1
I have tested this to work on raspberrypi4-64. Is this something that
should be supported in oe-core or should it be added via bbappend?
[-- Attachment #2: Type: text/html, Size: 2255 bytes --]
next reply other threads:[~2023-05-19 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 15:54 Markus Volk [this message]
2023-05-19 16:11 ` [OE-core] widevine + arm64 Ross Burton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=IJXWUR.OUXJ6LSOIO482@t-online.de \
--to=f_l_k@t-online.de \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.