Bug#337692: libx11-dev: encounter same error when trying to compile different X dependant software
Hoi!
Michel Dänzer wrote:
On Tue, 2006-05-02 at 23:55 +0200, Daniel Baulig wrote:
Package: libx11-dev
Version: 2:1.0.0-6
Followup-For: Bug #337692
I tried to compile different software using X headers (eg wmxmms,
wmpower and the dri radeon drivers) and encountered the same problem in
each of the compilation steps. It's always complaining about
/usr/include/X11/Xlib.h:3578: error: syntax error before '_X_SENTINEL'
_X_SENTINEL is defined in /usr/include/X11/Xfuncproto.h here. Maybe you
have a stray Xfuncproto.h lying around somewhere?
I already figured, that not Xlib.h but Xfuncproto.h seems to cause the
problem. I found a patch on the internet that was written for the
Xfuncproto.h of X11R6, which should solve the problem (the stuff I found
googling seems to handle exactly this bug, but only that it's from
x11r6) - I checked and Xfuncproto.h from my xorg7 already contains this
patch. Note, that this file contains the _X_SENTINEL definition!
I searched for packets providing extra Xfuncproto.h headers using dpkg
-S Xfuncproto.h but only found X11-proto-core-dev, which provided the
file I checked.
To be sure I then did find / -name Xfuncproto.h and after getting myself
a cup of coffee it indeed stumbled over antoher two Xfuncproto.h files.
The one of the extra two files that I think could cause the error is
indeed not yet patched. I didnt try patching it yet, because I would
rather like to get my compiler to use the correct file instead of
patching the wrong one.
I just checked the configure.ac file of one of the programs I tried to
compile and indeed it uses /usr/local/include (the path of the wrong
Xfuncproto.h) instead of /usr/include. However, I'm not sure where the
files really should be and I don't know how to change the path from
/usr/local/include to /usr/include - except of course by doing it
manually. I tried to find something with google, but I think I just dont
use the correct keywords to find what I'm looking for.
Maybe any suggestions, links or google keywords for me?
Greets
Daniel
Reply to: