From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 59332] New: Problems building 32bit Mesa
Date: Mon, 14 Jan 2013 02:43:25 +0000 [thread overview]
Message-ID: <bug-59332-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 848 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=59332
Priority: medium
Bug ID: 59332
Assignee: dri-devel@lists.freedesktop.org
Summary: Problems building 32bit Mesa
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: mike@fireburn.co.uk
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 72977
--> https://bugs.freedesktop.org/attachment.cgi?id=72977&action=edit
32bit build log
I can no longer build a 32bit mesa on my 64bit system
I'm using the same options and using master on both builds
I think this might have something to do with the autotools merge
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2253 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 reply other threads:[~2013-01-14 2:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 2:43 bugzilla-daemon [this message]
2013-01-14 8:47 ` [Bug 59332] Problems building 32bit Mesa bugzilla-daemon
2013-01-16 2:33 ` bugzilla-daemon
2013-01-19 3:51 ` bugzilla-daemon
2013-01-27 13:07 ` bugzilla-daemon
2013-01-30 23:47 ` bugzilla-daemon
2013-01-31 8:03 ` bugzilla-daemon
2013-01-31 8:13 ` bugzilla-daemon
2013-01-31 18:46 ` bugzilla-daemon
2013-01-31 18:49 ` bugzilla-daemon
2013-01-31 19:44 ` bugzilla-daemon
2013-02-01 9:17 ` bugzilla-daemon
2013-02-05 21:05 ` bugzilla-daemon
2013-02-05 21:26 ` 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-59332-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.