Compilers For The Zaurus, Compiling should be easy! Options

[snowfarthing]

Zaurus seems to lack straightforward tools for development.

This last couple of weeks I tried to compile an altered version of IRK (so that I could type Dvorak on my Targus and experiment with the layout). I didn't get very far, though, because I couldn't figure out what I needed to set up a compiling environment in a timely manner. I'm not even sure whether I could use Bitbake, or how to set up a non-2.95 cross-compiler (since I use OpenZaurus 3.5.4)!

It would be very nice if a tarball could be made that will set up all the needed tools immediately, all in one go, so that all that would be necessary would be to type something like

CODE

./configure
zmake

or something like

CODE

gcc-zaurus myprog.cpp

to cross-compile something for the Zaurus.

Furthermore, I would really like to be able to compile things in OpenZaurus directly, in an emulator, using a native compiler toolchain. I know from experience that it is very discouraging to try to set up such an environment! It would be really nice to be able to install a zaurus-compiler.ipk package that will give a hobbyist make, gcc, and so forth, the ability to try to compile whatever programs that tickles their fancy (particularly math programs in my case).

When I originally got my Zaurus, I looked forward to being able to do things like this. It's a little frustrating that doing this is just out of my reach! (But I still like my Zaurus; between Python and the fact that I can request something like this makes my Zaurus much closer to that ideal than a Palm or my old Windows-CE Cassiopeia!)

[snowfarthing]

It should all be built automatically for you when you issue (in your case): bitbake irk

It took me a while to figure this out, but it should be bitbake irk-targus. I had to google a little bit and look at stuff/org.openembedded.dev/packages to figure this out.

Nonetheless, I really appreciate the help! It's taking a while, but bitbake is happily compiling now.
------------------------
Update: bitbake didn't finish compiling. It ran into an error, and put out the following output:

CODE

| make[2]: arm-linux-gcc-2.95: Command not found
| make[2]: *** [constants.h] Error 127
| make[2]: Leaving directory `/home/am9385/open_embedded/tmp/work/collie-linux/openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r23/linux/arch/arm/tools'
| make[1]: *** [dep] Error 2
| make[1]: Leaving directory `/home/am9385/open_embedded/tmp/work/collie-linux/openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r23/linux/arch/arm/tools'
| make: *** [archdep] Error 2
| FATAL: oe_runmake failed
NOTE: Task failed: /home/am9385/open_embedded/tmp/work/collie-linux/openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r23/temp/log.do_compile.18311
NOTE: package openzaurus-sa-2.4.18-rmk7-pxa3-embedix-r23: task do_compile: failed
ERROR: TaskFailed event exception, aborting
NOTE: package openzaurus-sa-2.4.18-rmk7-pxa3-embedix: failed
ERROR: Build of irk-targus failed

Do I need to install the gcc-2.95 compiler then? It was my understanding that OpenZaurus had moved on to a later version of gcc. (I'll have to check the documentation when I have the time.)