Package: pixmap
Severity: serious
Justification: FTBFS

pixmap FTBFS:

  make[1]: Entering directory `/build/build/pixmap-2.6pl4'
  gcc -m32 -g -O2 -fno-strict-aliasing      -I. -I.. -I/usr/X11R6/include/X11 
-I/usr/include/ -I/usr/X11R6/include    -Dlinux -D__i386__ 
-D_POSIX_C_SOURCE=199309L                           -D_POSIX_SOURCE 
-D_XOPEN_SOURCE           -D_BSD_SOURCE -D_SVID_SOURCE                          
       -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64                               
                -DFUNCPROTO=15 -DNARROWPROTO     -DUSE_ATHENA 
-DAPPDEFDIR=\"/etc/X11/app-defaults\"                      
-DRGBF=\"/usr/X11R6/lib/X11/rgb.txt\"    -c -o PixEdit.o PixEdit.c
  In file included from /usr/X11R6/include/X11/Intrinsic.h:56,
                   from PixEdit.c:62:
  /usr/X11R6/include/X11/Xlib.h:3578: error: syntax error before '_X_SENTINEL'
  /usr/X11R6/include/X11/Xlib.h:3578: warning: data definition has no type or 
storage class
  /usr/X11R6/include/X11/Xlib.h:3583: error: syntax error before '_X_SENTINEL'
  /usr/X11R6/include/X11/Xlib.h:3583: warning: data definition has no type or 
storage class
 (etc.)

The _X_SENTINEL macro in newer X.Org is defined in Xfuncproto.h (it is
used for a gcc4 attribute in certain functions); however, pixmap ships
its own versions, pulled in with -I.:

  trofast:/usr/src/pixmap-2.6pl4# ls -l X11
  total 12
  -rw-r----- 1 163 users 2263 1991-10-15 14:28 Xfuncproto.h
  -rw-r----- 1 163 users 1665 1991-10-15 14:28 Xfuncs.h
  -rw-r----- 1 163 users 2394 1991-10-15 14:28 Xosdefs.h

Shipping X headers from 1999 inside the upstream package is, of course,
utter insanity, but I have no idea why it does this, or what the best
fix would be. :-)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.3
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to