Re: BUG: GLib-Genmarshal-WARNING **: unknown type: VARIANT

[Yasushi SHOJI <yashi atmark-techno com>]

Hi Steven,

At Mon, 11 Apr 2011 01:22:29 +0100,
Steven Swann wrote:
> 
> Hello All,
> 
> I believe I have found a bug.
> 
> Background:
> I am cross-compiling glib for an ARM11 target. I have built the 
> toolchain loosely on the CLFS book.
> I am looking to get OPIE running on the board and as such, require Glib.
> 
> I have compiled a number of versions of glib as follows:
> 
> glib-2.14.5        -        Compiled
> glib-2.20.5        -        Compiled
> glib-2.24.2        -        Compiled
> glib-2.25.0        -        Failed - different error
> glib-2.25.17      -        Failed
> glib-2.26.1        -        Failed
> glib-2.27.4        -        Failed
> glib-2.28.3        -        Failed
> glib-2.28.5        -        Failed
> 
> The error in question is as follows:
> Making all in gobject
> make[2]: Entering directory `/mnt/armclfs/sources/glib-2.28.5/gobject'
>    CC     glib-genmarshal.o
>    CCLD   glib-genmarshalafter
> ../glib/.libs/libglib-2.0.so: warning: the use of OBSOLESCENT `utime' is 
> discouraged, use `utimes'
> make glib-genmarshal
> make[3]: Entering directory `/mnt/armclfs/sources/glib-2.28.5/gobject'
> make[3]: `glib-genmarshal' is up to date.
> make[3]: Leaving directory `/mnt/armclfs/sources/glib-2.28.5/gobject'
>    GEN    stamp-gmarshal.h
> 
> (process:22042): GLib-Genmarshal-WARNING **: unknown type: VARIANT

it seems like glib-genmarshal does not know VARIANT.  but not sure why
it happens if you cross compile. with make V=1 should show like this.
my arm cross env chocked on qsort check in configure ;-p.  so, this is
on my x86_64 with git tip.  it might differ from yours:

	make glib-genmarshal
	make[3]: Entering directory `/home/yashi/src/glib/gobject'
	make[3]: `glib-genmarshal' is up to date.
	make[3]: Leaving directory `/home/yashi/src/glib/gobject'
	echo "#ifndef __G_MARSHAL_H__" > xgen-gmh \
	        && echo "#define __G_MARSHAL_H__" >> xgen-gmh \
	        && ./glib-genmarshal --nostdinc --prefix=g_cclosure_marshal ./gmarshal.list --header >> xgen-gmh \
	        && echo "#endif /* __G_MARSHAL_H__ */" >> xgen-gmh \
	        && (cmp -s xgen-gmh gmarshal.h 2>/dev/null || cp xgen-gmh gmarshal.h) \
	        && rm -f xgen-gmh xgen-gmh~ \
	        && echo timestamp > stamp-gmarshal.h
	./glib-genmarshal --nostdinc --prefix=g_cclosure_marshal ./gmarshal.list --body >> xgen-gmc \
	        && cp xgen-gmc gmarshal.c \
	        && rm -f xgen-gmc xgen-gmc~
	
so, would you mind to run glib-genmarshal by hand to double check?

now, if glib-genmarshal really does not know about VARIANT, there
might be some build issue.  you can run glib-genmarshal under gdb to
see why.

or, can you just run git bisect on glib-2.24.2 (good) and glib-2.25.17
(bad)?

thanks,
-- 
            yashi