Just to let you know: I had my armel debian running in qemu for more than 24 hours building qt4. It took like 15 hours for the qtwebkit alone, so I broke up, because there was no chance that this would come to an end within a reasonable period of time...
I think I'll give up on the whole qemu approach. It was interesting to play around with qemu and debian for the first time in my life. But this setup will not serve my purposes.
My next approach will be scratchbox2. I'm gonna setup x86 debian inside of VirtualBox and use a chroot-like scratchbox environment to cross compile with the official freescale arm-linux-gcc etc. This looks really promising. Maybe I can even use the qt sdk provided by onyx inside the scratchbox and thus avoid rebuilding qt4.
In the meantime, I found out that we won't be able to build pyside with onyx' qt sdk, because it depends on QtXmlPatterns. I don't know yet whether PyQt will run without it. At least, PySide can be built with an embedded qt version at all. (PyQt has huge problems when built without X11.) So maybe I will end up recompiling Qt 4.7.3 embedded, but with QtXmlPatterns.
EDIT: There is one thing that I learned from using the debian armel stuff: Everything (especially all the binaries) that's released for debian armel runs on our M92 - at least concerning the architecture. The only reason why we can't just start using the debian armel deb files is that they heavily rely on lots of shared libraries we lack (and thus would have to pack on our M92's memory). But maybe the time will come when this compatibility turns out useful
