sane-project-website/old-archive/1997-05/0081.html

185 wiersze
8.1 KiB
HTML

<!-- received="Sat Jun 14 17:11:44 1997 MST" -->
<!-- sent="Sun, 15 Jun 97 00:45:28 +0100" -->
<!-- name="Neville Wilford" -->
<!-- email="jnw@phaedrus.demon.co.uk" -->
<!-- subject="Sane on NeXT/OpenStep - a plea for help" -->
<!-- id="199706142345.AAA03373@phaedrus.demon.co.uk" -->
<!-- inreplyto="" -->
<title>sane-devel: Sane on NeXT/OpenStep - a plea for help</title>
<h1>Sane on NeXT/OpenStep - a plea for help</h1>
<b>Neville Wilford</b> (<a href="mailto:jnw@phaedrus.demon.co.uk"><i>jnw@phaedrus.demon.co.uk</i></a>)<br>
<i>Sun, 15 Jun 97 00:45:28 +0100</i>
<p>
<ul>
<li> <b>Messages sorted by:</b> <a href="date.html#81">[ date ]</a><a href="index.html#81">[ thread ]</a><a href="subject.html#81">[ subject ]</a><a href="author.html#81">[ author ]</a>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0082.html">Michael K. Johnson: "Re: Sane on NeXT/OpenStep - a plea for help"</a>
<li> <b>Previous message:</b> <a href="0080.html">David Mosberger-Tang: "SANE v0.6 released!"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0082.html">Michael K. Johnson: "Re: Sane on NeXT/OpenStep - a plea for help"</a>
<li> <b>Maybe reply:</b> <a href="0082.html">Michael K. Johnson: "Re: Sane on NeXT/OpenStep - a plea for help"</a>
<li> <b>Reply:</b> <a href="0083.html">Gordon Matzigkeit: "Re: Sane on NeXT/OpenStep - a plea for help"</a>
<!-- reply="end" -->
</ul>
<!-- body="start" -->
Greetings fellow list-members.<br>
<p>
My apologies for the length of this message.<br>
<p>
I am a recent convert to OpenStep/Intel 4.0, a multi-platform <br>
descendent of NeXTStep. This is a mach-based OS having an appealing <br>
GUI on top of what is essentially BSD 4.3. Generic SCSI devices are <br>
supported.<br>
<p>
I would love to be able to compile SANE for OpenStep in order to use <br>
the Mustek scanner I have. One of the linux mustek drivers has been <br>
ported to NeXTStep but this doesn't support my scanner. I have <br>
searched the list archives for any mention of NeXT without success.<br>
<p>
The difficulty lies in the fact that I am very much a programming <br>
neophyte. I have been trying without much understanding to compile <br>
sane-0.55, 0.57 and the very latest 0.6. With any of these I can <br>
use configure to create what look like reasonable Makefiles and <br>
config.h, but I suspect that vital things may be missing and their <br>
absence isn't even apparent to me:<br>
<p>
phaedrus&gt; ./configure<br>
creating cache ./config.cache<br>
checking for gcc... no<br>
checking for cc... cc<br>
checking whether the C compiler (cc ) works... yes<br>
checking whether the C compiler (cc ) is a cross-compiler... no<br>
checking whether we are using GNU C... yes<br>
checking whether cc accepts -g... yes<br>
checking for a BSD compatible install... /usr/bin/install -c<br>
checking whether make sets ${MAKE}... yes<br>
checking how to run the C preprocessor... cc -E -traditional-cpp<br>
checking whether cc needs -traditional... no<br>
checking for AIX... no<br>
checking for minix/config.h... no<br>
checking for POSIXized ISC... no<br>
checking for ANSI C header files... yes<br>
checking for fcntl.h... yes<br>
checking for unistd.h... yes<br>
checking for libintl.h... no<br>
checking for sys/scanio.h... no<br>
checking for scsi.h... no<br>
checking for sys/scsi.h... no<br>
checking for sys/scsiio.h... no<br>
checking for scsi/sg.h... no<br>
checking for /usr/src/linux/include/scsi/sg.h... no<br>
checking for working const... yes<br>
checking for size_t... yes<br>
checking for ssize_t... no<br>
checking for working alloca.h... no<br>
checking for alloca... yes<br>
checking for unistd.h... (cached) yes<br>
checking for getpagesize... yes<br>
checking for working mmap... no<br>
checking for atexit... yes<br>
checking for ioperm... no<br>
checking for mkdir... yes<br>
checking for scsireq_enter... no<br>
checking for strdup... no<br>
checking for strndup... no<br>
checking for strftime... yes<br>
checking for strstr... yes<br>
checking for strsep... no<br>
checking for strtod... yes<br>
checking for snprintf... no<br>
checking host system type... i386-next-nextstep4<br>
checking for ranlib... ranlib<br>
checking for cc option to produce PIC... -fPIC<br>
checking for broken GCC collect2... no<br>
checking for cc option to statically link programs... -static<br>
checking if ld is GNU ld... no<br>
checking if ld supports shared libraries... no<br>
checking how to hardcode library paths into programs... unsupported<br>
checking for ld option to reload object files... -r<br>
checking dynamic linker characteristics... no<br>
checking if libtool supports shared libraries... no<br>
checking whether to build shared libraries... no<br>
checking whether to build static libraries... yes<br>
creating libtool<br>
checking for X... no<br>
checking for sqrt in -lm... yes<br>
checking for gettext in -lintl... no<br>
checking for gethostbyaddr in -lnsl... no<br>
checking for socket in -lsocket... no<br>
checking for main in -lXext... no<br>
checking for main in -lX11... no<br>
checking for main in -lXpm... no<br>
checking for main in -lglib... no<br>
checking for main in -lgdk... no<br>
checking for gtk_check_button_new in -lgtk... no<br>
checking for libgimp/gimp.h... no<br>
checking for dlfcn.h... no<br>
enabling Mustek line-distance bug workaround<br>
disabling PINT backend<br>
disabling QuickCam backend<br>
preloading backends into DLL<br>
updating cache ./config.cache<br>
creating ./config.status<br>
creating Makefile<br>
creating lib/Makefile<br>
creating sanei/Makefile<br>
creating frontend/Makefile<br>
creating backend/Makefile<br>
creating include/Makefile<br>
creating doc/Makefile<br>
creating include/sane/config.h<br>
<p>
The compile looks fine until sanei_save_values.c<br>
....<br>
echo timestamp &gt; sanei_codec_bin.lo<br>
cc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include <br>
-DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d <br>
-DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=0 -DV_MINOR=5 -g -O2 <br>
-D_GNU_SOURCE sanei_save_values.c<br>
sanei_save_values.c: In function `sanei_save_values':<br>
sanei_save_values.c:64: `read' undeclared (first use this function)<br>
sanei_save_values.c:64: (Each undeclared identifier is reported only once<br>
sanei_save_values.c:64: for each function it appears in.)<br>
sanei_save_values.c:65: `write' undeclared (first use this function)<br>
*** Exit 1<br>
Stop.<br>
*** Exit 1<br>
Stop.<br>
<p>
It looks to my untutored eye as though something important might be <br>
missing from OpenStep's SCSI support, but how would I know.<br>
<p>
Can anyone advise me whether this is completely a lost cause? Are <br>
there any subscribers to the list with NeXT/OpenStep experience?<br>
<p>
Once again apologies for the length of this - I'm sure the last <br>
thing many of you want to see is the output of a configure command - <br>
but it seemed like the only way to make what little information I <br>
have available to people who might understand it.<br>
<p>
Many Thanks,<br>
Neville Wilford<br>
<p>
<pre>
--
Internet: <a href="mailto:jnw@phaedrus.demon.co.uk">jnw@phaedrus.demon.co.uk</a> CompuServe: 100042,3501
<a href="mailto:j.n.wilford@ncl.ac.uk">j.n.wilford@ncl.ac.uk</a> PGP 2.x public key available
<p>
<pre>
--
Source code, list archive, and docs: <a href="http://www.azstarnet.com/~axplinux/sane/">http://www.azstarnet.com/~axplinux/sane/</a>
To unsubscribe: mail -s unsubscribe <a href="mailto:sane-devel-request@listserv.azstarnet.com">sane-devel-request@listserv.azstarnet.com</a>
</pre>
<!-- body="end" -->
<p>
<ul>
<!-- next="start" -->
<li> <b>Next message:</b> <a href="0082.html">Michael K. Johnson: "Re: Sane on NeXT/OpenStep - a plea for help"</a>
<li> <b>Previous message:</b> <a href="0080.html">David Mosberger-Tang: "SANE v0.6 released!"</a>
<!-- nextthread="start" -->
<li> <b>Next in thread:</b> <a href="0082.html">Michael K. Johnson: "Re: Sane on NeXT/OpenStep - a plea for help"</a>
<li> <b>Maybe reply:</b> <a href="0082.html">Michael K. Johnson: "Re: Sane on NeXT/OpenStep - a plea for help"</a>
<li> <b>Reply:</b> <a href="0083.html">Gordon Matzigkeit: "Re: Sane on NeXT/OpenStep - a plea for help"</a>
<!-- reply="end" -->
</ul>