From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104607] Mesa fails to build in OBS after c797cd605ac9cb42795a40b1967b6dd10184b763
Date: Fri, 12 Jan 2018 18:39:26 +0000 [thread overview]
Message-ID: <bug-104607-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1115 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104607
Bug ID: 104607
Summary: Mesa fails to build in OBS after
c797cd605ac9cb42795a40b1967b6dd10184b763
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: network723@rkmail.ru
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 136691
--> https://bugs.freedesktop.org/attachment.cgi?id=136691&action=edit
Don't look at me
Mesa fails to build with openSUSE build service after the commit
c797cd605ac9cb42795a40b1967b6dd10184b763 with message 'I: Program returns
random data in a function \n E: Mesa no-return-in-nonvoid-function
si_shader.c:1967'
I had to make some changes to si_shader.c to make it build again, however I had
no idea what I was doing.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2702 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
next reply other threads:[~2018-01-12 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 18:39 bugzilla-daemon [this message]
2018-01-12 18:43 ` [Bug 104607] Mesa fails to build in OBS after c797cd605ac9cb42795a40b1967b6dd10184b763 bugzilla-daemon
2018-01-12 19:22 ` bugzilla-daemon
2018-03-31 23:53 ` 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-104607-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.