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 92301] Unigine Sanctuary freeze-crashes R390X
Date: Fri, 09 Oct 2015 08:48:05 +0000	[thread overview]
Message-ID: <bug-92301-502-iXtlLioz74@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92301-502@http.bugs.freedesktop.org/>


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

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

--- Comment #14 from Michel Dänzer <michel@daenzer.net> ---
(In reply to MC Return from comment #12)
> I set those env vars, but the result was exactly the same - sanctuary
> crashed the machine after a few seconds running, but it showed these errors
> after changing screens to console mode:

Thanks, but as I said, we need to see the corresponding terminal / log output
from Sanctuary.

(In reply to MC Return from comment #13)
> Nope --enable-32-bit is no longer recognized and I could not find any
> instructions on how to ensure a 32bit build...
> What flags do I need to add to ./autogen.sh or what needs to be done to to
> get that accomplished ?

I use:

--host=i386-linux-gnu --with-llvm-prefix=[path to 32-bit llvm directory]
'CC=gcc -m32' 'CXX=g++ -m32'

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

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

  parent reply	other threads:[~2015-10-09  8:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 21:15 [Bug 92301] Unigine Sanctuary freeze-crashes R390X bugzilla-daemon
2015-10-06  1:33 ` bugzilla-daemon
2015-10-06  8:21 ` bugzilla-daemon
2015-10-06  8:25 ` bugzilla-daemon
2015-10-06  8:32 ` bugzilla-daemon
2015-10-06  8:48 ` bugzilla-daemon
2015-10-06  8:55 ` bugzilla-daemon
2015-10-06  9:18 ` bugzilla-daemon
2015-10-06  9:26 ` bugzilla-daemon
2015-10-07  3:39 ` bugzilla-daemon
2015-10-07  3:48 ` bugzilla-daemon
2015-10-07 10:05 ` bugzilla-daemon
2015-10-07 10:12 ` bugzilla-daemon
2015-10-07 10:26 ` bugzilla-daemon
2015-10-09  8:48 ` bugzilla-daemon [this message]
2015-10-09 12:07 ` bugzilla-daemon
2015-10-09 12:23 ` 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-92301-502-iXtlLioz74@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