All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107990] Got Dying Light working in Arch by changing Mesa's compile steps, how to get it working Out Of the Box?
Date: Wed, 19 Sep 2018 14:25:21 +0000	[thread overview]
Message-ID: <bug-107990-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 107990
           Summary: Got Dying Light working in Arch by changing Mesa's
                    compile steps, how to get it working Out Of the Box?
           Product: Mesa
           Version: 18.2
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: john.ettedgui@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Hello,

I've been looking for a while on how to get DL running on Arch and I finally
found it.

Now I'd like this to be possible by default, but I don't know if the issue lies
in Arch or Mesa and I'm hopeful someone here will be able to help.

Arch's default compiler flags are:

CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong
-fno-plt"
CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong
-fno-plt"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"

"-fno-plt" in C/CXXFLAGS and ",-z,now" in LDFLAGS need to be unset when
compiling Mesa to get DL to not crash.

The other change required is to not use glvnd, with "-D glvnd=false". I tried
building libglvnd with the same flags as Mesa, or none at all, but it didn't
help.

Here's the original 18.2.0 PKGBUILD in case it helps:
https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/mesa

The behavior is the same with Mesa 18.2.0 or master, with LLVM 6.0 or master.
I haven't tried with autoconf though, only Meson, but I can try if you think
it'd be helpful.

I don't have any helpful log, as the game segfaults without these, a backtrace
in gdb doesn't show me anything useful, and there's nothing in dmesg.

I'm using a 280X but people with 5xx seem to have the same behavior, so I don't
think it depends on the model. We're all on amdgpu.

I'd be happy to try / provide whatever would help.

Current versions: Linux 4.18.8, GCC 8.2.1, glibc 2.28, but it failed in
previous ones too.

Thank you!

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

[-- Attachment #1.2: Type: text/html, Size: 3846 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-09-19 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 14:25 bugzilla-daemon [this message]
2018-09-19 23:13 ` [Bug 107990] Got Dying Light working in Arch by changing Mesa's compile steps, how to get it working Out Of the Box? bugzilla-daemon
2018-09-20  2:50 ` bugzilla-daemon
2018-09-20  4:12 ` bugzilla-daemon
2018-09-28  1:03 ` bugzilla-daemon
2018-10-18 23:32 ` bugzilla-daemon
2018-11-29  4:21 ` bugzilla-daemon
2019-01-12 22:38 ` bugzilla-daemon
2019-01-19 19:29 ` bugzilla-daemon
2019-01-31  8:26 ` bugzilla-daemon
2019-01-31 10:45 ` bugzilla-daemon
2019-02-01 12:09 ` bugzilla-daemon
2019-06-29  1:42 ` bugzilla-daemon
2019-07-01 16:35 ` 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-107990-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.