From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109714] Unable to Compile R200 driver: "Options 'r200' are not allowed..."
Date: Thu, 21 Feb 2019 15:30:03 +0000 [thread overview]
Message-ID: <bug-109714-502-a87BFO0cnk@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109714-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1311 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109714
Adam Jackson <ajax@nwnk.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOTABUG
Status|NEW |RESOLVED
--- Comment #1 from Adam Jackson <ajax@nwnk.net> ---
(In reply to moriel5 from comment #0)
> When attempting to compile Mesa with the R200 driver, on Solus, Meson spits
> out the following error: ERROR: Options "r200" are not in allowed choices:
> ", auto, kmsro, radeonsi, r300, r600, nouveau, freedreno, swrast, v3d, vc4,
> etnaviv, tegra, i915, svga, virgl, swr, panfrost".
That's the list of gallium drivers. r200 is not a gallium driver, it's a
"classic" DRI driver:
datura:~/git/mesa% meson configure build | grep r200
dri-drivers [auto] [, auto, i915, i965, r100, r200, nouveau,
swrast]
List of dri drivers to build. If this is set to auto all drivers applicable
to the target OS/architecture will be built
You want 'meson configure build -Ddri-drivers=r200'.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2996 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-02-21 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 11:27 [Bug 109714] Unable to Compile R200 driver: "Options 'r200' are not allowed..." bugzilla-daemon
2019-02-21 15:30 ` bugzilla-daemon [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=bug-109714-502-a87BFO0cnk@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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