From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mesa: update to 20.3.1.
Date: Sat, 19 Dec 2020 06:25:14 +0100 [thread overview]
Message-ID: <20201219052514.Jp6wGKR9vWItjW5VLiHbM5McmMuljJmTqRQzC25v8TE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27214@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
New comment by q66 on void-packages repository
https://github.com/void-linux/void-packages/pull/27214#issuecomment-748422197
Comment:
we should fix the driver search path according to https://github.com/void-linux/void-packages/pull/27269 while at it
basically remove
```
case "$XBPS_TARGET_MACHINE" in
i686) configure_args+=" -Ddri-drivers-path=/usr/lib32/dri";;
esac
```
and add `-Ddri-drivers-path=/usr/lib${XBPS_TARGET_WORDSIZE}` to `configure_args`
next prev parent reply other threads:[~2020-12-19 5:25 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 2:57 [PR PATCH] " HadetTheUndying
2020-12-17 14:06 ` [PR REVIEW] " ericonr
2020-12-17 14:07 ` ericonr
2020-12-17 14:08 ` ericonr
2020-12-17 14:08 ` ericonr
2020-12-17 20:50 ` [PR PATCH] [Updated] " HadetTheUndying
2020-12-17 20:51 ` HadetTheUndying
2020-12-17 20:51 ` [PR REVIEW] " HadetTheUndying
2020-12-17 21:05 ` ericonr
2020-12-18 2:49 ` [PR PATCH] [Updated] " HadetTheUndying
2020-12-19 5:25 ` q66 [this message]
2020-12-20 1:47 ` travankor
2020-12-20 1:51 ` HadetTheUndying
2020-12-20 1:58 ` ericonr
2020-12-20 2:07 ` HadetTheUndying
2020-12-20 3:37 ` ericonr
2020-12-20 3:45 ` HadetTheUndying
2020-12-20 3:45 ` [PR PATCH] [Closed]: " HadetTheUndying
2020-12-20 3:37 [PR PATCH] " ericonr
2020-12-21 14:53 ` st3r4g
2020-12-21 14:56 ` st3r4g
2020-12-21 14:57 ` ericonr
2020-12-21 15:01 ` st3r4g
2020-12-21 15:02 ` st3r4g
2020-12-21 17:50 ` q66
2020-12-21 17:50 ` q66
2020-12-22 5:25 ` ericonr
2020-12-22 5:25 ` ericonr
2020-12-22 23:44 ` st3r4g
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=20201219052514.Jp6wGKR9vWItjW5VLiHbM5McmMuljJmTqRQzC25v8TE@z \
--to=q66@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).