Is There A Programme Called 'od' In The C3100 Os

[BarrySamuels]

Nobody has been able to help with ImageMagick and TIFF support so I've resorted to trying to compile my own version of ImageMagick 5.4.6. I've chosen that version because it can use the version of libtiff I've installed on the Zaurus.

During the Make step it keeps looking for 'od' which is on my desktop under /usr/bin but does not appear to be present on the Zaurus. Is it necessary? The compilation progresses quite happily without it.

This isn't my main problem which is that the compilation fails with an I/O error    but I wondered whether it might be associated.

[gds]

During the Make step it keeps looking for 'od' which is on my desktop under /usr/bin but does not appear to be present on the Zaurus. Is it necessary? The compilation progresses quite happily without it.

This isn't my main problem which is that the compilation fails with an I/O error    but I wondered whether it might be associated.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=102458\"][{POST_SNAPBACK}][/a][/div]

Hi Barry,

/usr/bin/od is present on my 3100 (cacko rom - perhaps it's missing in the Sharp rom?)

It's just the octal dump program, you should be able to build it from the GNU coreutils package if you really need it. I thought there was a version built in to busybox, but maybe not.

PS - on the IO error. It's just a thought, but could it be /tmp filling up (and therefore writes failing)? When compiling some things I found /tmp way too small; it fills up quickly. Setting the TMPDIR environment variable helped.

[BarrySamuels]

During the Make step it keeps looking for 'od' which is on my desktop under /usr/bin but does not appear to be present on the Zaurus. Is it necessary? The compilation progresses quite happily without it.

This isn't my main problem which is that the compilation fails with an I/O error    but I wondered whether it might be associated.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=102458\"][{POST_SNAPBACK}][/a][/div]

Hi Barry,

/usr/bin/od is present on my 3100 (cacko rom - perhaps it's missing in the Sharp rom?)

It's just the octal dump program, you should be able to build it from the GNU coreutils package if you really need it. I thought there was a version built in to busybox, but maybe not.

PS - on the IO error. It's just a thought, but could it be /tmp filling up (and therefore writes failing)? When compiling some things I found /tmp way too small; it fills up quickly. Setting the TMPDIR environment variable helped.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=102533\"][{POST_SNAPBACK}][/a][/div]

Thanks for the suggestions gds. What restricts the size of /tmp?

Since posting that plea for help I've discovered an .ipk package for a slightly later version of ImageMagick that does cope with TIFF files. The silly thing is that it was a waste of time. ImageMagick, on the Zaurus, takes 2 minutes and 35 seconds to convert just 1 image which becomes totally impractical when dealing with 10 at a time. I was hoping to run a batch job on a camera card.  

VisualQ on the other hand takes 20 seconds to convert and reduce. It's a pity it doesn't, apparently, have a command line interface.

[gds]

PS - on the IO error. It's just a thought, but could it be /tmp filling up (and therefore writes failing)? When compiling some things I found /tmp way too small; it fills up quickly. Setting the TMPDIR environment variable helped.

Thanks for the suggestions gds. What restricts the size of /tmp?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=102541\"][{POST_SNAPBACK}][/a][/div]

By default /tmp is really a link into the /dev/shm ramdisk. This makes sense from a flash-wear point of view (and perhaps speed/power consumption as well, I don't know). The initial size (set in rc.rofilesys to 1Mb, I think) is large enough for most uses of /tmp, but gcc can sometimes create very large intermediate files and expects /tmp to be able to take them.