From: faithanalog <faithanalog@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: llvmpipe is not enabled for i686
Date: Sun, 12 Jun 2022 08:38:50 +0200 [thread overview]
Message-ID: <20220612063850.q165-LOpK_8XvCpvk0AhjOfSyAIwneJkWhYbvheItcI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37349@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
New comment by faithanalog on void-packages repository
https://github.com/void-linux/void-packages/issues/37349#issuecomment-1153084725
Comment:
would love to this fixed because it affects my poulsbo hardware (intel atom netbook, no working hardware acceleration unless you use a 3.x kernel and a proprietary module/userspace). Me and a few friends use these things on the regular and we either custom compile mesa or use other distributions which have llvmpipe enabled (like debian).
anyways the fix is a one-liner, just
```
diff --git a/srcpkgs/mesa/template b/srcpkgs/mesa/template
index c90500de74..172d9c12ff 100644
--- a/srcpkgs/mesa/template
+++ b/srcpkgs/mesa/template
@@ -32,7 +32,7 @@ fi
# especially on big endian it's all kinds of broken, and e.g. on
# 32-bit powerpc it does not work at all, so fall back to softpipe
case "$XBPS_TARGET_MACHINE" in
- x86_64*|aarch64*|ppc64le*|arm*) ;;
+ i686*|x86_64*|aarch64*|ppc64le*|arm*) ;;
*) configure_args+=" -Ddraw-use-llvm=false" ;;
esac
```
next prev parent reply other threads:[~2022-06-12 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 5:52 [ISSUE] " sham1
2022-05-30 5:55 ` sham1
2022-05-30 5:56 ` sham1
2022-06-12 6:33 ` faithanalog
2022-06-12 6:38 ` faithanalog [this message]
2022-07-18 17:50 ` [ISSUE] [CLOSED] " sham1
2022-07-18 17:50 ` sham1
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=20220612063850.q165-LOpK_8XvCpvk0AhjOfSyAIwneJkWhYbvheItcI@z \
--to=faithanalog@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).