From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102014] Mesa git build broken by commit bc7f41e11d325280db12e7b9444501357bc13922
Date: Wed, 02 Aug 2017 12:54:05 +0000 [thread overview]
Message-ID: <bug-102014-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2124 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102014
Bug ID: 102014
Summary: Mesa git build broken by commit
bc7f41e11d325280db12e7b9444501357bc13922
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: marko.skender@protonmail.com
QA Contact: dri-devel@lists.freedesktop.org
Hello,
Current git build is seemingly broken by:
[ 511s] pipe_radeonsi.c: In function 'create_screen':
[ 511s] pipe_radeonsi.c:15:34: error: 'flags' undeclared (first use in this
function); did you mean 'fabs'?
[ 511s] rw = amdgpu_winsys_create(fd, flags, radeonsi_screen_create);
[ 511s] ^~~~~
[ 511s] fabs
[ 511s] pipe_radeonsi.c:15:34: note: each undeclared identifier is reported
only once for each function it appears in
[ 511s] make[4]: *** [Makefile:996: pipe_radeonsi.lo] Error 1
[ 511s] make[4]: *** Waiting for unfinished jobs....
[ 511s] pipe_r600.c: In function 'create_screen':
[ 511s] pipe_r600.c:12:38: error: 'flags' undeclared (first use in this
function); did you mean 'fabs'?
[ 511s] rw = radeon_drm_winsys_create(fd, flags, r600_screen_create);
[ 511s] ^~~~~
[ 511s] fabs
[ 511s] pipe_r600.c:12:38: note: each undeclared identifier is reported only
once for each function it appears in
[ 511s] pipe_r300.c: In function 'create_screen':
[ 511s] pipe_r300.c:12:39: error: 'flags' undeclared (first use in this
function); did you mean 'fabs'?
[ 511s] sws = radeon_drm_winsys_create(fd, flags, r300_screen_create);
[ 511s] ^~~~~
[ 511s] fabs
Regards,
Marko
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3500 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:[~2017-08-02 12:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 12:54 bugzilla-daemon [this message]
2017-08-02 12:57 ` [Bug 102014] Mesa git build broken by commit bc7f41e11d325280db12e7b9444501357bc13922 bugzilla-daemon
2017-08-02 12:57 ` bugzilla-daemon
2017-08-02 12:58 ` bugzilla-daemon
2017-08-02 14:25 ` bugzilla-daemon
2017-08-02 15:29 ` bugzilla-daemon
2017-08-02 23:32 ` bugzilla-daemon
2017-08-03 7:17 ` bugzilla-daemon
2017-08-03 8:23 ` bugzilla-daemon
2017-08-03 9:49 ` bugzilla-daemon
2017-08-03 13:52 ` 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-102014-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.