Bug 25550 - [gallium] intel_drm_fence.c does not compile
Summary: [gallium] intel_drm_fence.c does not compile
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: All Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-09 16:26 UTC by Johannes Obermayr
Modified: 2009-12-09 18:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Johannes Obermayr 2009-12-09 16:26:38 UTC 
I have not been able to compile Mesa for more than 24 hours (It was possible 48 hours ago...):

[full log] ~1.3 MiB
http://download762.mediafire.com/mrm0hlnmd29g/wyww2tivrly/Build.log

[short log]
<snip>
gmake[5]: Entering directory `/usr/src/packages/BUILD/Mesa/src/gallium/winsys/drm/intel/gem'
gcc -c -I. -I../../../../../../src/gallium/include -I../../../../../../src/gallium/auxiliary -I../../../../../../src/gallium/drivers -I/src/gallium/include -I/src/gallium/auxiliary -I/src/gallium/drivers -I/usr/include/drm -march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -Wall -Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -fPIC -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -D_GNU_SOURCE -DPTHREADS -DHAVE_POSIX_MEMALIGN -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS intel_drm_batchbuffer.c -o intel_drm_batchbuffer.o
gcc -c -I. -I../../../../../../src/gallium/include -I../../../../../../src/gallium/auxiliary -I../../../../../../src/gallium/drivers -I/src/gallium/include -I/src/gallium/auxiliary -I/src/gallium/drivers -I/usr/include/drm -march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -Wall -Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -fPIC -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -D_GNU_SOURCE -DPTHREADS -DHAVE_POSIX_MEMALIGN -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS intel_drm_buffer.c -o intel_drm_buffer.o
gcc -c -I. -I../../../../../../src/gallium/include -I../../../../../../src/gallium/auxiliary -I../../../../../../src/gallium/drivers -I/src/gallium/include -I/src/gallium/auxiliary -I/src/gallium/drivers -I/usr/include/drm -march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -Wall -Wmissing-prototypes -std=c99 -ffast-math -fno-strict-aliasing -fPIC -DUSE_X86_ASM -DUSE_MMX_ASM -DUSE_3DNOW_ASM -DUSE_SSE_ASM -D_GNU_SOURCE -DPTHREADS -DHAVE_POSIX_MEMALIGN -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DGLX_DIRECT_RENDERING -DGLX_INDIRECT_RENDERING -DHAVE_ALIAS intel_drm_fence.c -o intel_drm_fence.o
intel_drm_fence.c: In function 'intel_drm_fence_reference':
intel_drm_fence.c:42: error: dereferencing pointer to incomplete type
gmake[5]: *** [intel_drm_fence.o] Error 1
gmake[5]: Leaving directory `/usr/src/packages/BUILD/Mesa/src/gallium/winsys/drm/intel/gem'
gmake[4]: *** [default] Error 1
gmake[4]: Leaving directory `/usr/src/packages/BUILD/Mesa/src/gallium/winsys/drm/intel'
gmake[3]: *** [default] Error 1
gmake[3]: Leaving directory `/usr/src/packages/BUILD/Mesa/src/gallium/winsys/drm'
gmake[2]: *** [default] Error 1
gmake[2]: Leaving directory `/usr/src/packages/BUILD/Mesa/src/gallium/winsys'
gmake[1]: *** [subdirs] Error 1
gmake[1]: Leaving directory `/usr/src/packages/BUILD/Mesa/src'
gmake: *** [default] Error 1
error: Bad exit status from /var/tmp/rpm-tmp.991 (%install)
<snip>
Comment 1 Roland Scheidegger 2009-12-09 18:54:13 UTC 
oops sorry for that, missed that dereference of opaque type. Apparently I forgot to compile intel winsys when doing the pipe_reference changes...
Fixed by 71f4267ac23f52dcc94590cb94c3e0ce451662aa.

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.