| Summary: | Can't build xcb-util-0.3.0 | ||
|---|---|---|---|
| Product: | XCB | Reporter: | Michael Stevens <mstevens> |
| Component: | Utils | Assignee: | Jamey Sharp <jamey> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | CC: | julien |
| Version: | 1.1 | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Michael Stevens
2008-09-18 09:49:35 UTC
Can you try with 0.3.1? Tested again with 0.3.1, I see what looks like the same failure: gcc -DPACKAGE_NAME=\"xcb-util\" -DPACKAGE_TARNAME=\"xcb-util\" -DPACKAGE_VERSION=\"0.3.1\" "-DPACKAGE_STRING=\"xcb-util 0.3.1\"" -DPACKAGE_BUGREPORT=\"xcb@lists.freedesktop.org\" -DPACKAGE=\"xcb-util\" -DVERSION=\"0.3.1\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DHAVE_VASPRINTF=1 -I. -I/usr/local/include -I/usr/local/include -I../aux -Wall -g -O2 -MT libxcb_image_la-xcb_image.lo -MD -MP -MF .deps/libxcb_image_la-xcb_image.Tpo -c xcb_image.c -fPIC -DPIC -o .libs/libxcb_image_la-xcb_image.o In file included from xcb_image.c:33: ../aux/xcb_bitops.h:51: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ ../aux/xcb_bitops.h:72: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ ../aux/xcb_bitops.h:97: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ ../aux/xcb_bitops.h:114: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ ../aux/xcb_bitops.h:132: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ ../aux/xcb_bitops.h:155: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ ../aux/xcb_bitops.h:174: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ ../aux/xcb_bitops.h:199: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ In file included from xcb_image.c:36: xcb_pixel.h:54: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ xcb_pixel.h:69: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ xcb_pixel.h:82: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ xcb_pixel.h:94: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ xcb_pixel.h:104: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ xcb_pixel.h:113: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ xcb_pixel.h:121: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ xcb_pixel.h:134: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ xcb_pixel.h:147: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ xcb_pixel.h:159: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘static’ xcb_image.c: In function ‘xcb_image_annotate’: xcb_image.c:128: warning: implicit declaration of function ‘xcb_roundup’ xcb_image.c: In function ‘xcb_image_create’: xcb_image.c:240: warning: implicit declaration of function ‘xcb_mask’ xcb_image.c: In function ‘xcb_image_get’: xcb_image.c:341: warning: implicit declaration of function ‘xcb_bit_reverse’ make[1]: *** [libxcb_image_la-xcb_image.lo] Error 1 make[1]: Leaving directory `/tmp/xcb-util-0.3.1/image' make: *** [all-recursive] Error 1 mstevens@tetra:/tmp/xcb-util-0.3.1 Ok, you need x11proto-7.0.8 at least, that's why it fails I guess. Which version do you have? I've pushed a fix by checking xproto version in git. Not sure which package you mean, is this the one? Installed Packages Name : xorg-x11-proto-devel Arch : i386 Version: 7.1 Release: 9.el5.centos Size : 1.2 M Repo : installed Summary: X.Org X11 Protocol headers Description: X.Org X11 Protocol headers It seems so. pkg-config --modversion xproto ? > pkg-config --modversion xproto
7.0.7
Which would fit with the "needs 7.0.8".
|
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.