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 75929] New: Configuring Mesa to use shared libLLVM.so fails
Date: Sat, 08 Mar 2014 22:58:29 +0000	[thread overview]
Message-ID: <bug-75929-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 75929
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Configuring Mesa to use shared libLLVM.so fails
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: rankincj@googlemail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Drivers/Gallium/r600
           Product: Mesa

Created attachment 95379
  --> https://bugs.freedesktop.org/attachment.cgi?id=95379&action=edit
Patch for configure.ac to fix building against libLLVM.so

Configuring Mesa to build on Fedora 20 with the shared libLLVM.so is ignoring
the new --enable-llvm-shared-libs option. It looks like two references to
"with_llvm_shared_libs" were missed in configure.ac.

I have attached a patch.

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

[-- Attachment #1.2: Type: text/html, Size: 2491 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

             reply	other threads:[~2014-03-08 22:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-08 22:58 bugzilla-daemon [this message]
2014-03-09  2:45 ` [Bug 75929] Configuring Mesa to use shared libLLVM.so fails bugzilla-daemon
2014-03-09 13:47 ` bugzilla-daemon
2014-03-11 17:10 ` bugzilla-daemon
2014-03-18 13:29 ` 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-75929-502@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