gobject-introspection can't compile with endian.h

[Steve Kargl]

On Mon, Dec 27, 2010 at 09:04:30PM +0200, Ivan Klymenko wrote:
> ?? Mon, 27 Dec 2010 10:00:47 -0800
> Steve Kargl <sgk at troutmask.apl.washington.edu> ??????????:
> 
> > On a keep new install of freebsd9, I run into

s/keep/completely

> > 
> > ===>  Vulnerability check disabled, database not found
> > ===>  License check disabled, port has not defined LICENSE
> > ===>  Extracting for gobject-introspection-0.9.12
> > => No checksum file (/usr/ports/devel/gobject-introspection/distinfo).
> > ===>  Patching for gobject-introspection-0.9.12
> > ===>   gobject-introspection-0.9.12 depends on package: libtool>=2.2
> >...
> > - found ===>  Applying FreeBSD patches for
> > gobject-introspection-0.9.12 ===>   gobject-introspection-0.9.12
> > CC     g_ir_compiler-compiler.o CCLD   g-ir-compiler CC
> > g_ir_generate-generate.o CCLD   g-ir-generate
> >   GEN    g-ir-scanner
> >   GEN    g-ir-annotation-tool
> > gmake[2]: Leaving directory
> > `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.9.12/tools'
> > Making all in gir gmake[2]: Entering directory
> > `/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.9.12/gir'
> > GISCAN GLib-2.0.gir /usr/include/machine/endian.h:107: syntax error,
> > unexpected '{' in ' return (__extension__ ({ register __uint32_t __X
> > = (_x); __asm ("bswap %0" : "+r" (__X)); __X; }));' at
> > '{' /usr/include/machine/endian.h:107: syntax error, unexpected ';'
> > in ' return (__extension__ ({ register __uint32_t __X = (_x); __asm
> > ("bswap %0" : "+r" (__X)); __X; }));' at ';' GISCAN GObject-2.0.gir
> >...
> > How does one fix this?
> > 
> 
> I have a similar problem ...
> And it applies not only to the port to which you have a problem ...
> It seems that the problem appeared after updating the source code of
> the system ...
> 

Yep.  A web search suggests that anything vaguely X11 related
will eventually pull in a GNOME related component, which pulls
in gobject-introspection.  The search also suggests that this
problem has been known for more than year except apparently
no gnome developer sees the problem or knows how to fix it.

-- 
Steve