From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79338] Something's broken after llvm's svn commit 209067
Date: Wed, 28 May 2014 10:09:26 +0000 [thread overview]
Message-ID: <bug-79338-502-B5mM7xFlMp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-79338-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1757 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=79338
--- Comment #4 from José Suárez <j.suarez.agapito@gmail.com> ---
Thank you for your quick reply, Michel.
The ppa I use is llvm.org's ppa (llvm.org/apt/) for Ubuntu 14.04 so I guess it
will just be plain upstream with no additional patches.
With regard to compiling, I have two chroot environments, one is i386 and the
other one is amd64, which I use to recompile mesa (from oibaf's ubuntu ppa)
with llvm 3.5 via dpkg-buildpackage (previously editing debian/rules so that
the config looks for llvm 3.5 rather than llvm 3.4).
I have tried to compile the original tar.gz packages (dpkg-buildpackage) from
the llvm.org ppa within those two chroot environments but I just can't get them
to work (config fails complaining about llvm tools, if I remember correctly,
even though I downloaded all the tar.gz packages in the ppa and among which
there was a package named llvm extra tools or something like that). Using
apt-source results in obtaining the llvm 3.4 source tarball from Ubuntu's
repositories, not the one from llvm.org, so that does not help either. I think
that manually compiling llvm is a bit too much for me (I am not that advanced),
so I'll try to get the dpkg-buildpackage working. If that doesn't work I guess
I'll give a look at manually compiling.
I have never used apitrace either but I will try to find instructions and give
it a go.
I currently don't have too much free time due to real life (TM) but I'll try to
address the llvm compilation (and bisect) and apitrace test. I'll also check
newer llvm builds from the ppa in order to check if the problem has been
solved.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2558 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:[~2014-05-28 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 23:21 [Bug 79338] New: Something's broken after llvm's svn commit 209067 bugzilla-daemon
2014-05-27 23:36 ` [Bug 79338] " bugzilla-daemon
2014-05-27 23:37 ` bugzilla-daemon
2014-05-28 2:58 ` bugzilla-daemon
2014-05-28 10:09 ` bugzilla-daemon [this message]
2014-05-29 8:19 ` bugzilla-daemon
2014-05-29 21:22 ` bugzilla-daemon
2014-05-29 21:33 ` bugzilla-daemon
2014-05-29 22:22 ` 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-79338-502-B5mM7xFlMp@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;
as well as URLs for NNTP newsgroup(s).