From: xeroxslayer <xeroxslayer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] webrtc-audio-processing: fix for i686-musl build
Date: Thu, 25 Jul 2024 12:53:23 +0200 [thread overview]
Message-ID: <20240725105323.0DD5524ACC@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51424@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
There is an updated pull request by xeroxslayer against master on the void-packages repository
https://github.com/xeroxslayer/void-packages webrtc-audio-processing
https://github.com/void-linux/void-packages/pull/51424
webrtc-audio-processing: fix for i686-musl build
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture: x86_64-musl, i686-musl (with `-A i686-musl`)
- I built this PR locally for these architectures:
- x86_64 (`-A x86_64` on x86_64-musl)
- i686 (`-A i686` on x86_64-musl)
- aarch64 (`-A x86_64 -a aarch64` on x86_64-musl)
- aarch64-musl (`-A x86_64-musl -a aarch64-musl` on x86_64-musl)
- armv7l (`-A i686 -a armv7l` on x86_64-musl)
- armv7l-musl (`-A i686-musl -a armv7l-musl` on x86_64-musl)
A patch file from https://github.com/void-linux/void-packages/pull/51424.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-webrtc-audio-processing-51424.patch --]
[-- Type: text/x-diff, Size: 0 bytes --]
prev parent reply other threads:[~2024-07-25 10:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 14:25 [PR PATCH] " xeroxslayer
2024-07-24 14:29 ` [PR REVIEW] " classabbyamp
2024-07-24 14:34 ` [PR PATCH] [Updated] " xeroxslayer
2024-07-24 14:35 ` [PR REVIEW] " abenson
2024-07-24 14:48 ` abenson
2024-07-24 20:40 ` xeroxslayer
2024-07-25 10:47 ` [PR PATCH] [Updated] " xeroxslayer
2024-07-25 10:53 ` [PR PATCH] [Closed]: " xeroxslayer
2024-07-25 10:53 ` xeroxslayer [this message]
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=20240725105323.0DD5524ACC@inbox.vuxu.org \
--to=xeroxslayer@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).