You've just shortened my workload, I believe. I was setting this
up for a future test in conjunction with imagemagick; but, based
on your advice, I think I'll pass on the rest of the sane-backends, etc.
build. Users are currently able to make movies, etc. from the imagemagick
built without scanimage support. All other imagemagick requirements
built and installed fine. sane-backends, etc. would have built fine too.
But, from your experience, it wouldn't have been useable.
Thanks again for the help and advice.
Regards,
Philip
->Actually, I just realized that you may be running towards a dead end
->here. What is the hardware you want to use with SANE? What connection
->does it use? A while back, I tried to run SANE on Tru64 myself. I
->failed, here is why:
->- SCSI: officially (DEC/Compaq), SCSI scanners are not supported by
-> Tru64. SANE does have support for Tru64 support, but it's rather
-> fragile (at least 1.0.4 wasn't stable on Tru64 4.0E, IIRC).
->- USB and IEEE-1394 are unsupported by Tru64 anyway, as far as I know.
->- I don't think you can do anything useful with the Tru64 parallel
-> port apart from printing to a printer.
->- that leaves the only useable port the serial port, and I know that
-> that works under Tru64 pretty much the same way as under Linux.
->The way I do it at the moment is to have a Linux machine act as a scan
->server, using the SCSI bus to connect to a scanner. The Tru64 machines
->just use the net backend to connect to it. If you use a similar
->set-up, you will not need all the ieee1284, jpeg, and gphoto2 stuff
->under Tru64 anyway. And most of this should be trivial under Linux
->(which runs on the scan server).
-> Andras
