Created attachment 271635 [details] build.log for gdk-pixbuf with introspection USE flag enabled during cross-compilation All ebuilds, which contain the introspection USE flag enabled, fail to cross-compile because of this flag. I will attach an example build.log for gdk-pixbuf failure.
As seen googling a bit, this looks to be an upstream problem... but I couldn't find any upstream solution for the problem :S
There is at least a hint for the direction a solution could go, see bug 371717 comment 4 The binary /usr/bin/g-ir-scanner uses a fixed path independend from the environment. This needs to be adjusted to use the right libdir (e.g. /usr/lib64 on amd64, /usr/lib32 for crosscomiling 32bit libs on amd64).
*** Bug 386935 has been marked as a duplicate of this bug. ***
Arbitrary cross-compiling with gobject-introspection is basically impossible at the moment: g-ir-scanner compiles and executes a temporary binary, and that only works if target binaries can run on your build machine. Proper multilib support, on the other hand, is almost certainly doable. Probably the most invasive change that's required is splitting /usr/share/gir-1.0/ into ABI-specific directories (there is no guarantee that .gir files for different ABIs are fully compatible; for example, GLib-2.0.gir has some differences between amd64 and x86).
(In reply to comment #3) > *** Bug 386935 has been marked as a duplicate of this bug. *** for multilib-portage users doing cross-compilation on amd64 for x86: I have added support for seperate binaries for each target ABI, so once you recompiled gobject-introspection, you should be able to cross-compile packages with introspection USE flag enabled.
I will close this bug for now, since the change from my last comment seems to remove all issues i have seen with gobject-introspection.
