From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: mednafen: fix build, add ppc patches, altivec option
Date: Thu, 25 Jul 2019 00:20:55 +0200 [thread overview]
Message-ID: <20190724222055.1REppP-Swwud3OmL8GY-eyTT6TIsVgsj5rxZcAy6z0k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13313@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
There's a merged pull request on the void-packages repository
mednafen: fix build, add ppc patches, altivec option
https://github.com/void-linux/void-packages/pull/13313
Description: Previously, mednafen wouldn't even build (on any platform) because of the aclocal related issues and also that the libcdio option hasn't existed in it in ages (i.e. drop superfluous dependency and remove). So fixed that + added an altivec option for ppc (enabled by default on ppc64, otherwise disabled) and ppc64 elfv2 libco impl from bsnes/higan (mednafen uses a very old forked version of bsnes, but the backport works fine). Also fixed lint.
prev parent reply other threads:[~2019-07-24 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 11:44 [PR PATCH] " voidlinux-github
2019-07-24 22:20 ` voidlinux-github [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=20190724222055.1REppP-Swwud3OmL8GY-eyTT6TIsVgsj5rxZcAy6z0k@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).