[Lsb-infrastructure] new headers: Xft/Xrender seem to be the issuenow
Wichmann, Mats D
mats.d.wichmann at intel.com
Fri Apr 25 07:14:08 PDT 2008
There seem to be some real generation errors here.
I'm guessing this is probably bad data that's suddenly
getting exposed by newer-better-more complete scripts...
> /opt/lsb/include/X11/extensions/Xrender.h:159: error: expected
identifier or '(' before ';' token
this line is: Xtrapeziod *;
> /opt/lsb/include/X11/extensions/Xrender.h:166: warning: unnamed
struct/union that defines no instances
yes, a structure that ends up being: struct { <some-stuff> };
> /opt/lsb/include/X11/extensions/Xrender.h:173: error: conflicting type
qualifiers for 'XRenderColor'
this one is: const typedef struct { <some-stuff> } XrenderColor;
> /opt/lsb/include/X11/extensions/Xrender.h:94: error: previous
declaration of 'XRenderColor' was here
yes, this is a redfine.
> /opt/lsb/include/X11/extensions/Xrender.h:180: error: expected '=',
',', ';', 'asm' or '__attribute__' before '*' token
this one is: const typedef struct { <some-stuff> } *XrenderColor;
> /opt/lsb/include/X11/extensions/Xrender.h:187: warning: unnamed
struct/union that defines no instances
same as earlier instance
and the list goes on from here, this is just clearly broken.
> In file included from unit.2.c:16:
> /opt/lsb/include/X11/Xft/Xft.h:68: error: expected identifier or '('
before ';' token
this stuff is similar to the Xrender problems.
More information about the lsb-infrastructure
mailing list