dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68544] cannot build mesa 9.2 without llvm
Date: Mon, 26 Aug 2013 00:15:20 +0000	[thread overview]
Message-ID: <bug-68544-502-N3P9qQbYBv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68544-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 679 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=68544

--- Comment #2 from Emil Velikov <emil.l.velikov@gmail.com> ---
Seems like test always priorities the _and_ over _or_ :)

Kris' patch does the right thing, although it can be simplified to either:

test "x$HAVE_GALLIUM_I915" = xyes -o "x$HAVE_GALLIUM_SOFTPIPE" = xyes && test
"x$MESA_LLVM" = x1

or

test "x$HAVE_GALLIUM_I915" = xyes -a "x$MESA_LLVM" = x1 -o
"x$HAVE_GALLIUM_SOFTPIPE" = xyes -a "x$MESA_LLVM" = x1

Feel free to test either one(all three :P) and send the git patch to the ML
mesa-dev@lists.freedesktop.org

Thanks for spotting this :)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1565 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-08-26  0:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-25 20:10 [Bug 68544] New: cannot build mesa 9.2 without llvm bugzilla-daemon
2013-08-25 21:18 ` [Bug 68544] " bugzilla-daemon
2013-08-26  0:15 ` bugzilla-daemon [this message]
2013-08-26 16:20 ` bugzilla-daemon
2013-08-26 21:47 ` bugzilla-daemon
2013-08-26 21:56 ` bugzilla-daemon
2013-08-26 22:20 ` bugzilla-daemon
2013-08-27  5:13 ` bugzilla-daemon

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-68544-502-N3P9qQbYBv@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