From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 47875] Making r600_dri.so fails when building 32bit on 64bit
Date: Mon, 26 Mar 2012 05:32:19 +0000 [thread overview]
Message-ID: <bug-47875-502-BUtuCAIdBQ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-47875-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=47875
--- Comment #1 from Alexandre Demers <alexandre.f.demers@gmail.com> 2012-03-25 22:32:19 PDT ---
After testing, I can confirm the problem comes from "export
LIBDRM_LIBS=/usr/lib/i386-linux-gnu/". When it is not set, the build goes all
the way to the end.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-03-26 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 0:35 [Bug 47875] New: Making r600_dri.so fails when building 32bit on 64bit bugzilla-daemon
2012-03-26 5:32 ` bugzilla-daemon [this message]
2012-03-26 5:33 ` [Bug 47875] Making r600_dri.so fails when building 32bit on 64bit when setting LIBDRM_LIBS (maybe other env vars also) manually: missing -L bugzilla-daemon
2012-03-26 7:22 ` bugzilla-daemon
2012-03-26 12: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-47875-502-BUtuCAIdBQ@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