2004-11-03-trunk on SuSE 8.2 Linux, after bypassing the build bustage in bug 1767 I am getting the following build error: -- snip -- gcc -m32 -c -g -DDEBUG_gismobile -ansi -pedantic -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wundef -fno-merge-constants -I../include -I../../../exports/include/X11 -I../../../include/fonts -I../../../include/extensions -I../../../programs/Xserver/Xext -I../../../programs/Xserver/lbx -I../../.. -I../../../exports/include -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP -DXCSECURITY -DTOGCUP -DXF86BIGFONT -DDPMSExtension -DPIXPRIV -DPANORAMIX -DRENDER -DRANDR -DXFIXES -DDAMAGE -DCOMPOSITE -DXEVIE -DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH -DXFreeXDGA -DXvExtension -DXFree86LOADER -DXFree86Server -DXF86VIDMODE -DXvMCExtension -DSMART_SCHEDULE -DBUILDDEBUG -DXResExtension -DX_BYTE_ORDER=X_LITTLE_ENDIAN -DXORG_VERSION_CURRENT="(((6) * 10000000) + ((8) * 100000) + ((1) * 1000) + 99)" -DNDEBUG -DFUNCPROTO=15 -DNARROWPROTO dispatch.c In file included from dispatch.c:104: ../../../programs/Xserver/Xext/panoramiXsrv.h:17: error: parse error before '*' token ../../../programs/Xserver/Xext/panoramiXsrv.h:17: warning: type defaults to `int' in declaration of `PanoramiXFindIDByScrnum' ../../../programs/Xserver/Xext/panoramiXsrv.h:17: error: ISO C forbids data definition with no type or storage class ../../../programs/Xserver/Xext/panoramiXsrv.h:18: error: parse error before '*' token ../../../programs/Xserver/Xext/panoramiXsrv.h:18: warning: type defaults to `int' in declaration of `PanoramiXFindIDOnAnyScreen' ../../../programs/Xserver/Xext/panoramiXsrv.h:18: error: ISO C forbids data definition with no type or storage class In file included from dispatch.c:116: ../../../include/extensions/XKBsrv.h:253: warning: redundant redeclaration of `noXkbExtension' in same scope ../include/globals.h:185: warning: previous declaration of `noXkbExtension' dispatch.c: In function `ProcCreateGC': dispatch.c:1571: warning: comparison between signed and unsigned dispatch.c: In function `ProcChangeGC': dispatch.c:1594: warning: comparison between signed and unsigned dispatch.c: In function `ProcCopyPlane': dispatch.c:1801: warning: comparison between signed and unsigned dispatch.c: In function `ProcUninstallColormap': dispatch.c:2584: warning: comparison between signed and unsigned dispatch.c: In function `ProcSetFontPath': dispatch.c:3472: warning: comparison between signed and unsigned make[5]: *** [dispatch.o] Error 1 make[5]: Leaving directory `/home/gismobile/projects/xorg/work007/xc/programs/Xserver/dix' make[4]: *** [dix] Error 2 make[4]: Leaving directory `/home/gismobile/projects/xorg/work007/xc/programs/Xserver' make[3]: *** [all] Error 2 make[3]: Leaving directory `/home/gismobile/projects/xorg/work007/xc/programs' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/gismobile/projects/xorg/work007/xc' make[1]: *** [World] Error 2 make[1]: Leaving directory `/home/gismobile/projects/xorg/work007/xc' make: *** [World] Error 2 -- snip -- The Debian tinderbox is suffering from the same problem... ;-(
Created attachment 1215 [details] List of files which should be removed It seems that many previously dead files are walking again on earth (er... CVS trunk). They were never properly cvs removed, the RCS backing files just had an invalid default branch set, which prevented CVS from checking them out. After fixing the RCS backing files the files re-appeared in CVS trunk and now need to be removed.
Created attachment 1217 [details] Commit log Patch checked-in.
Marking bug as FIXED. The tinderbox machines are GREEN again since the commit and testing on various platforms show that the problems are gone.
Thanks very much for this.
*** Bug 1778 has been marked as a duplicate of this bug. ***
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.