Bug 90241

Summary: brw_fs.cpp error: integer constant is too large for ‘long’ type
Product: Mesa Reporter: Zenitur
Component: Drivers/DRI/i965Assignee: Ian Romanick <idr>
Status: RESOLVED FIXED QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: normal    
Priority: medium    
Version: 10.3   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Full build log

Description Zenitur 2015-04-29 15:51:06 UTC
Created attachment 115454 [details]
Full build log

I trying to make fresh graphical stack on some unsupported Linux distribution.

  CXX      brw_fs.lo
brw_fs.cpp:1720: error: integer constant is too large for ‘long’ type
brw_fs.cpp:3246: error: integer constant is too large for ‘long’ type
brw_fs.cpp:3263: error: integer constant is too large for ‘long’ type
[more]
brw_fs.cpp:3273: error: integer constant is too large for ‘long’ type
brw_fs.cpp:3274: error: integer constant is too large for ‘long’ type
brw_fs.cpp:3275: error: integer constant is too large for ‘long’ type
make[5]: *** [brw_fs.lo] Error 1

Linux 3.17.6 i686, Debian 5.0, GCC 4.3, Automake 1.14, fresh Xorg libs compiled with scripts from:

http://www.linuxfromscratch.org/blfs/view/svn/x/x7proto.html
http://www.linuxfromscratch.org/blfs/view/svn/x/x7lib.html

Mesa 10.3.7 (from ftp://ftp.freedesktop.org/pub/mesa/older-versions/10.x/10.3.7/) because of this page (https://01.org/linuxgraphics/downloads/2014/2014q3-intel-graphics-stack-release) recommends 10.3 with 3.16 Linux kernel. Configure string:

./configure CFLAGS='-O2' CXXFLAGS='-O2' --prefix=/home/username/xorg/xorg-build/ --enable-texture-float --enable-gles1 --enable-gles2 --enable-osmesa --enable-xa --enable-gbm --enable-glx-tls --enable-sysfs --with-egl-platforms="drm,x11" --with-dri-drivers="i965" --with-gallium-drivers=""

Full build log attached.
Comment 1 Zenitur 2015-04-30 19:22:41 UTC
I retest with Mesa 10.5.4. That was fixed!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.