Hi there, My apologies for posting the bug in the "core" components section, but there's no "gnome" section. I'm trying to build an image for my platform using OE version rocko, but the gobject-introspection component seems to hang forever during compilation. My host: Fedora 27 Target: sh4 Compiler: gcc 4.9.4 See the following log: https://pastebin.com/1ifJTQSE It used to build with morty.
rocko doesn't ship gcc 4.9.4 so is that an external toolchain that the SH4 BSP needs? g-i needs enabling by BSPs, so I'd suggest filing a bug with the BSP provider.
YP doesn't even provide a sh4 machine definition that I can try to reproduce with, so I too think this issue belongs with the BSP provider.
So let us know if there's a reasonable way we can try to reproduce and fix this, otherwise there's not much that can be done.
Gino, It would be great if you could ask the provider of the sh4 support to work with the YP to add sh4 support to oe-core and to join the community in supporting gobject-introspection and all of oe-core.
Hi, first of thank you for all the replies. My apologies for the late response, I have been busy for the past weeks. It was wrong submit a bug for a unsupported platform. Also there's nothing wrong with gobject-introspection at all. I already got it to work, so this bug can be closed. Some background information: My platform (digital satellite dvb receiver with STi 7xxx chipset) uses a SoC which is simply not properly supported anymore in newer versions of gcc/glibc. That's why we "downgrade" the version of gcc to 4.9.4 and glibc to 2.23 so we can keep building using this older toolchain. Reason for the gobject-introspection package not building properly is because qemu 2.10.0 refuses to boot when built for target sh4. And gobject-introspection recipe seems to rely on qemu for prorperly building the package. So downgrading qemu to 2.8.0 (the version used in Pyro) fixes this issue, allowing gobject-introspection (and everything else relying on qemu) to build again. So we now have a working image for our receiver again.
Thanks for reporting back. It's obviously a problem that new qemu doesn't work for sh4, have you reported that to the qemu maintainers?