From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 55604] New: r600_shader.c compile fails to compile with gcc-4.7.2
Date: Thu, 04 Oct 2012 08:37:52 +0000 [thread overview]
Message-ID: <bug-55604-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2607 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=55604
Priority: medium
Bug ID: 55604
Assignee: dri-devel@lists.freedesktop.org
Summary: r600_shader.c compile fails to compile with gcc-4.7.2
Severity: blocker
Classification: Unclassified
OS: Linux (All)
Reporter: treeve@sourcemage.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
mesalib git branch 9.0 fails to compile using scons
$ scons 2>ll
scons: Reading SConscript files ...
scons: Found LLVM version 3.1svn
Checking for X11 (x11 xext xdamage xfixes)... yes
Checking for XCB (x11-xcb xcb-glx >= 1.8.1)... yes
Checking for XF86VIDMODE (xxf86vm)... yes
Checking for DRM (libdrm >= 2.4.24)... yes
Checking for DRM_INTEL (libdrm_intel >= 2.4.30)... no
Checking for DRM_RADEON (libdrm_radeon >= 2.4.31)... yes
Checking for XORG (xorg-server >= 1.6.0)... yes
Checking for KMS (libkms >= 2.4.24)... no
Checking for UDEV (libudev > 150)... yes
Checking for C header file X11/extensions/dpmsconst.h... (cached) yes
scons: done reading SConscript files.
scons: Building targets ...
Compiling src/gallium/drivers/r600/r600_shader.c ...
Compiling src/gallium/drivers/r600/r700_asm.c ...
Compiling src/gallium/drivers/r600/r600_translate.c ...
scons: building terminated because of errors.
src/gallium/drivers/r600/r600_shader.c: At top level:
src/gallium/drivers/r600/r600_shader.c:210:44: error: array size missing in
'r600_shader_tgsi_instruction'
src/gallium/drivers/r600/r600_shader.c:210:76: error: array size missing in
'eg_shader_tgsi_instruction'
src/gallium/drivers/r600/r600_shader.c:210:106: error: array size missing in
'cm_shader_tgsi_instruction'
src/gallium/drivers/r600/r600_shader.c:741:2: warning: ISO C does not allow
extra ';' outside of a function [-pedantic]
src/gallium/drivers/r600/r600_shader.c: In function 'r600_shader_from_tgsi':
src/gallium/drivers/r600/r600_shader.c:1468:17: warning: comparison between
signed and unsigned integer expressions [-Wsign-compare]
src/gallium/drivers/r600/r600_shader.c:5221:2: warning: excess elements in
array initializer [enabled by default]
src/gallium/drivers/r600/r600_shader.c:5230:2: warning: (near initialization
for 'r600_shader_tgsi_instruction') [enabled by default]
scons reports that libkms not found, but libdrm-2.4.39 installs
/usr/lib/libkms.la
/usr/lib/libkms.so
/usr/lib/libkms.so.1
/usr/lib/libkms.so.1.0.0
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3940 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:[~2012-10-04 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 8:37 bugzilla-daemon [this message]
2019-09-18 19:01 ` [Bug 55604] r600_shader.c compile fails to compile with gcc-4.7.2 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-55604-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).