I invested my spare time in working with that crappy proprietary wink. I think it should be relabled to hog to make it obvious it is a memory hog. And like with any proprietary software you have not been granted the right to fix it for them. Anyway besides the memory issue wink feels really nice but if you can not generate the flash movie in the end this all doesn’t count. I’m currently waiting for the killall -9 wink to be executed so I can use my desktop again… fun.

My gcc patch works nicely with versions 3.4.4, 4.0.0, 4.0.2, 4.1.0 and 4.2.0 snapshot. This will greatly help finding issues with gcc when cross-compiling. A really bad error is when you compile for another endian and another libc and include headers of the host system. It is even worse if you run configure tests you are basicly configuring for your host system and not for your target. A lot of can go wrong if that happens, and since people use AMD64 to compile OpenEmbedded we see bugs coming up.

Oh and my favorite gcc option for now is -isystem, I will probably hack a -lsystem together to help OpenEmbedded. I have now at least two gcc hacks I should consider bringing into a submitable state as they are making gcc a better cross compiler.

Current Impressions:

• Will FSF leave the Google Summer of Code? Or will they trade Freedom for Money?
• Easily installing software into an ARM qemu image to test software quickly