Bug 100180

Summary: Build failure in GNOME Continuous
Product: Mesa Reporter: Emmanuele Bassi (:ebassi) <ebassi>
Component: OtherAssignee: mesa-dev
Status: RESOLVED FIXED QA Contact: mesa-dev
Severity: normal    
Priority: medium    
Version: git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Emmanuele Bassi (:ebassi) 2017-03-13 09:03:08 UTC
The GNOME Continuous delivery bot is failing to build Mesa with this error:

../../../../../src/gallium/drivers/svga/svga_format.c: In function 'check_format_tables':
../../../../../src/gallium/drivers/svga/svga_format.c:1842:7: error: size of unnamed array is negative
       STATIC_ASSERT(ARRAY_SIZE(format_conversion_table) == PIPE_FORMAT_COUNT);
       ^
Makefile:855: recipe for target 'svga_format.lo' failed

Full build log available: 

http://build.gnome.org/continuous/buildmaster/builds/2017/03/13/12/build/log-mesa.txt

Configuration options:

configure --build=x86_64-linux \
  --prefix=/usr --libdir=/usr/lib \
  --sysconfdir=/etc --localstatedir=/var \
  --bindir=/usr/bin --sbindir=/usr/bin \
  --datadir=/usr/share \
  --includedir=/usr/include \
  --libexecdir=/usr/libexec \
  --mandir=/usr/share/man \
  --infodir=/usr/share/info \
  --disable-static --disable-silent-rules \
  --host=x86_64-gnomeostree-linux \
  --disable-asm --enable-osmesa \
  --with-dri-driverdir=/usr/lib/dri \
  --enable-egl --enable-gles1 --enable-gles2 \
  --with-egl-platforms=wayland,x11,drm \
  --enable-shared-glapi --enable-gbm --enable-xa \
  --with-llvm-config-dir=/usr/bin/llvm3.3 \
  --with-gallium-drivers=svga,r300,nouveau,swrast,virgl \
  --enable-llvm --with-vulkan-drivers=intel \
  --with-dri-drivers=nouveau,radeon,r200,i915,i965,swrast

I've tagged Mesa to the previously successfully built commit:

https://cgit.freedesktop.org/mesa/mesa/commit/?id=920ab07566da8bbc95e12ed36da0c76f342066d9
Comment 1 Christian König 2017-03-13 11:50:33 UTC
Sorry for the inconvenience, code fix is upstream.

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.