Hi - I sent this message to Jeffrey Fox, the provider of the zgcc2 package, but thought it might be useful to share my triumph and issues to a wider audience.
Mike
-----
Jeffrey,
Many thanks for the zgcc2 package for the zaurus. On your web page, you mention that it is capable of compiling largish projects. I\'m pleased to report that I just waded through compiling python-2.3.3 entirely on my 5500. The source/build directory weighs in at 43 MB after all is said and done. I\'d say that qualifies :-)
I did note a few things that I thought I should report. (I\'m using the cramfs files you provided, BTW). Even though gcc --version reports 2.95.2, the python \"splash\" indicates 2.95.1. I haven\'t tracked it down, but perhaps your include files are from 2.95.1 or something similar?
More serious, I\'ve read several places that linking /usr/lib/libc.so to /lib/libc.so.6 is a Bad Idea because of missing static items. Apparently /usr/lib/libc.so is supposed to be a text file (not a link) with the single line
GROUP ( /lib/libc.so.6 libc_nonshared.a )
The file libc_nonshared.a (5950 bytes long) needs to be provided in /usr/lib (which can, of course, be a link to the real file elsewhere). I forgot where I found it, but I downloaded it from somewhere for the Z, and everything works fine. My build of python failed at the linking stage due to missing symbols (e.g. lstat64, etc.) until I implemented this.
I also had to add a link from /lib/libdl.so.2 to /usr/lib/libdl.so.
After implementing the above, the python compile went smoothly, and allowed me to then compile a CVS version of the python numarray package, which was my motivation for reinventing the wheel (compiling python when there are already several distributions for the Z out there).
I haven\'t tried compiling anything using qt, so I can\'t comment there. The installation instructions were clear and correct enough. No complaints there, either.
Thanks again for this magnificent piece of work. Now I can get back to developing in python :-)
