QUOTE(kopsis @ Mar 17 2005, 06:06 AM)
Sorry for not posting sooner ... I've been slammed with work lately. Cost growth estimates on a $50M embedded system development ... blech!
No sweat, that's life for you : priorities all wrong, most of the time
The libz.so that I use actually comes from a Debain devel package. If you know your way around Debian, you can download the appropriate ARM .deb file, extract its contents, and move the .so file to your Z. If not, I can probably whip up an IPK but not before this weekend. In the mean time you may want to post in the General Software forum to see if anyone has a copy of (or knows a feed for) the zlib package.
Kopsis, I guess I must have misunderstood something here, sorry.
The reason I posted in this forum, and to you in particular, is because I was under the impression that the problem was with your python 2.3.4 image for the Z, i.e. some missing item from the standard Python distribution. After all, the offending script fails specifically on "import zlib", the traceback ending with :
ImportErro: No module named zlib
On my Windows box there is a zlib.pyd in python/DLLs. On my gentoo (sort-of-debian) box there is a zlib.so in /usr/lib/python/lib-dynload. On my Z there is no zlib-something anywhere, so I thought it was just a Python problem.
I hadn't realised that under Linux (Windows seems to different, heh) you also need a system package (Gentoo has a lot of other zlib pieces all over the place). What I'm wondering is, if I find an arm version of zlib, will symlinking that zlib.so to the python lib-dynload dir be enough, or is there more involved ?
If you can save time by not creating a proper IPK, a plain copy of the relevant file(s) with some hints on where to copy/link them would do just as nicely for a start. And it's not like I'm in a hurry, either :-)