From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68468] 9.2.0rc2 Locks Under Various Conditions (UVD, Stress)
Date: Tue, 27 Aug 2013 16:02:55 +0000 [thread overview]
Message-ID: <bug-68468-502-tOSesyJGyv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68468-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1712 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=68468
--- Comment #4 from adam777@gmail.com ---
Well, the digging phase is over, I pretty much hit a wall.
As stated above, the general bisecting idea is clear, but I'm having problem
actually building mesa.
Here what I've done:
I downloaded the PKGBUILD and needed packages (clang-svn, llvm-svn etc.) from
Laurent Carlier's folder (an Arch developer).
I modified the PKGBUILD a bit - comment out unnecessary packages
(intel-dri-git, for example).
In order to build a specific commit, I added the following line to the build()
section:
cd ${srcdir}/mesa
git checkout 5b2855bfe79bfc3995969f2bf775d89b1bc1808a
makepkg -s was invoked later, but failed pretty soon. A bit of googling and the
blame was with bison 3.0.
Since the commit I'm trying to build is from April 11th and the bison 3.0 fix
is from July 31st and since I have no idea how to backport the bison 3.0
patches, I downgraded to bison 2.7.1 from the AUR
(https://bugs.freedesktop.org/show_bug.cgi?id=67354).
makepkg -s then got over the problematic bison part but failed again, this time
with an error related to llvm 3.4
(https://bugs.freedesktop.org/show_bug.cgi?id=64590).
Again, The fix is from May 14th (http://cgit.freedesktop.org/mesa/mesa/c …
773efbc181), so I reverted to LLVM 3.3 and modified PKGBUILD accordingly (llvm
instead of llvm-svn etc.).
This is, unfortunately, where I got stuck.
Build fails again, with an error that seems to be related to llvm 3.4, though
I'm on 3.3.
Log is here - http://pastebin.com/DwFAVKxC
PKGBUILD is here - http://pastebin.com/PwiZXVGv
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3067 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
next prev parent reply other threads:[~2013-08-27 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 8:17 [Bug 68468] New: 9.2.0rc2 Locks Under Various Conditions (UVD, Stress) bugzilla-daemon
2013-08-23 8:21 ` [Bug 68468] " bugzilla-daemon
2013-08-23 8:57 ` bugzilla-daemon
2013-08-23 21:12 ` bugzilla-daemon
2013-08-25 17:50 ` bugzilla-daemon
2013-08-27 16:02 ` bugzilla-daemon [this message]
2013-08-31 22:16 ` bugzilla-daemon
2013-08-31 22:17 ` [Bug 68468] 9.2.0 " bugzilla-daemon
2014-02-08 21:03 ` bugzilla-daemon
2019-09-18 19:05 ` 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-68468-502-tOSesyJGyv@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