From: abenson <abenson@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Intel media driver 22.4.4
Date: Sat, 23 Jul 2022 19:41:31 +0200 [thread overview]
Message-ID: <20220723174131.4Ngzr8s1DchU0VV13eUxFg8QosuYNr-le-r2jRQNPZo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38215@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
New comment by abenson on void-packages repository
https://github.com/void-linux/void-packages/pull/38215#issuecomment-1193161963
Comment:
This patch seems to fix `-musl`.
```
--- a/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp
+++ b/media_softlet/linux/common/os/osservice/mos_utilities_specific.cpp
@@ -51,7 +51,9 @@
#include <signal.h>
#include <unistd.h> // fork
#include <algorithm>
+#if defined(__GLIBC__)
#include <execinfo.h> // backtrace
+#endif
const char *MosUtilitiesSpecificNext::m_szUserFeatureFile = USER_FEATURE_FILE;
MOS_PUF_KEYLIST MosUtilitiesSpecificNext::m_ufKeyList = nullptr;
@@ -2489,6 +2491,7 @@
MOS_FreeMemory(pTraceBuf);
}
}
+#if defined(__GLIBC__)
if (m_mosTraceFilter & (1ULL << TR_KEY_CALL_STACK))
{
// reserve space for header and stack size field.
@@ -2508,6 +2511,7 @@
size_t ret = write(MosUtilitiesSpecificNext::m_mosTraceFd, traceBuf, nLen);
}
}
+#endif
}
return;
}
```
next prev parent reply other threads:[~2022-07-23 17:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 15:30 [PR PATCH] " motorto
2022-07-23 17:41 ` abenson [this message]
2022-07-23 17:48 ` motorto
2022-07-23 17:49 ` motorto
2022-07-23 17:54 ` motorto
2022-07-23 18:01 ` [PR PATCH] [Updated] " motorto
2022-07-24 15:25 ` [PR REVIEW] " sgn
2022-07-24 15:39 ` [PR PATCH] [Updated] " motorto
2022-07-24 15:41 ` [PR REVIEW] " motorto
2022-07-28 10:22 ` motorto
2022-07-28 14:54 ` [PR PATCH] [Merged]: " abenson
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=20220723174131.4Ngzr8s1DchU0VV13eUxFg8QosuYNr-le-r2jRQNPZo@z \
--to=abenson@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).