kopia lustrzana https://gitlab.com/sane-project/website
284 wiersze
11 KiB
HTML
284 wiersze
11 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
|
|
"http://www.w3.org/TR/REC-html40/loose.dtd">
|
|
<HTML>
|
|
<HEAD>
|
|
<TITLE>sane-devel: Re: ./configure xsane is failing?</TITLE>
|
|
<META NAME="Author" CONTENT="scc (fsanta@arrakis.es)">
|
|
<META NAME="Subject" CONTENT="Re: ./configure xsane is failing?">
|
|
</HEAD>
|
|
<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
|
|
<H1>Re: ./configure xsane is failing?</H1>
|
|
<!-- received="Sat Apr 21 11:25:29 2001" -->
|
|
<!-- isoreceived="20010421182529" -->
|
|
<!-- sent="Sat, 21 Apr 2001 02:55:50 +0200" -->
|
|
<!-- isosent="20010421005550" -->
|
|
<!-- name="scc" -->
|
|
<!-- email="fsanta@arrakis.es" -->
|
|
<!-- subject="Re: ./configure xsane is failing?" -->
|
|
<!-- id="01042102555000.00623@horche" -->
|
|
<!-- inreplyto="20010420224717.A13994@vortex.swb.de" -->
|
|
<STRONG>From:</STRONG> scc (<A HREF="mailto:fsanta@arrakis.es?Subject=Re:%20./configure%20xsane%20is%20failing?&In-Reply-To=<01042102555000.00623@horche>"><EM>fsanta@arrakis.es</EM></A>)<BR>
|
|
<STRONG>Date:</STRONG> Fri Apr 20 2001 - 17:55:50 PDT
|
|
<P>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0212.html">Marcel Pol: "Microtek scanner not working anymore"</A>
|
|
<UL>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0210.html">Onno Garms: "Snapscan 310 at Adaptec 1505 does not work"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0196.html">Henning Meier-Geinitz: "Re: ./configure xsane is failing?"</A>
|
|
<!-- nextthread="start" -->
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0213.html">Henning Meier-Geinitz: "Re: ./configure xsane is failing?"</A>
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0195.html">Massimo Maiurana: "Re: ./configure xsane is failing?"</A>
|
|
<LI><STRONG>Reply:</STRONG> <A HREF="0213.html">Henning Meier-Geinitz: "Re: ./configure xsane is failing?"</A>
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#211">[ date ]</A>
|
|
<A HREF="index.html#211">[ thread ]</A>
|
|
<A HREF="subject.html#211">[ subject ]</A>
|
|
<A HREF="author.html#211">[ author ]</A>
|
|
</UL>
|
|
<HR NOSHADE><P>
|
|
<!-- body="start" -->
|
|
<P>
|
|
Hi Henning Hi everyone.
|
|
<BR>
|
|
<P>Thanks for your time. I'll correct the errors right away.
|
|
<BR>
|
|
<P>The only reason that we used source is that we can keep up to date easier.
|
|
<BR>
|
|
With xsane and previously the gimp 1.1 series there were many updates and it
|
|
<BR>
|
|
was important for us in our changeover from crashintosh's that we had the
|
|
<BR>
|
|
very best that was available. All we can say is that the method we use works
|
|
<BR>
|
|
for us and our friends and that we have never had any niggles with it that
|
|
<BR>
|
|
many other users seem to have.
|
|
<BR>
|
|
<P>The only bit we don't understand is the bit about the /etc/ld.so.conf. We
|
|
<BR>
|
|
have never touched this file before. Where does it fit in?
|
|
<BR>
|
|
<P>Best wishes from all at FeF, Spain.
|
|
<BR>
|
|
<P><P>On Friday 20 April 2001 22:47, you wrote:
|
|
<BR>
|
|
<EM>> Hi,
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> On Fri, Apr 20, 2001 at 07:05:44AM +0200, scc wrote:
|
|
</EM><BR>
|
|
<EM>> > We put together a step by step guide for sane specifically for stuff like
|
|
</EM><BR>
|
|
<EM>> > this at:
|
|
</EM><BR>
|
|
<EM>> >
|
|
</EM><BR>
|
|
<EM>> > www.arrakis.es/~fsanta/sane/howto.html
|
|
</EM><BR>
|
|
<EM>> >
|
|
</EM><BR>
|
|
<EM>> > it has been tested with Mandrake too and it works but it would mean you
|
|
</EM><BR>
|
|
<EM>> > having to start over again with the installation.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> You are asking for suggestions on your page so here they are: :-)
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> * Maybe add a paragraph about why going through all the hassle of
|
|
</EM><BR>
|
|
<EM>> installing everything from source. Some distributions (e.g. SuSE
|
|
</EM><BR>
|
|
<EM>> 7.1) come with current packages of SANE so I would only recommend to
|
|
</EM><BR>
|
|
<EM>> compile SANE if something doesn't work. Same goes for gtk and gimp,
|
|
</EM><BR>
|
|
<EM>> I would only download and compile them if the installed binaries are
|
|
</EM><BR>
|
|
<EM>> too old to compile xsane.
|
|
</EM><BR>
|
|
<EM>> You write that glib and gtk that comes with the distribution
|
|
</EM><BR>
|
|
<EM>> should be removed. This will cause trouble with programs that came
|
|
</EM><BR>
|
|
<EM>> with the distribution and that are linked against gtk. I wouldn't
|
|
</EM><BR>
|
|
<EM>> recommend to do it if you aren't really shure what you are doing.
|
|
</EM><BR>
|
|
<EM>> In my experience the most problems of beginners when compiling
|
|
</EM><BR>
|
|
<EM>> SANE and a frontend are: Headers of X, gtk, gimp not installed.
|
|
</EM><BR>
|
|
<EM>> /usr/local/lib not in /etc/ld.so.conf. /usr/local/lib/sane in
|
|
</EM><BR>
|
|
<EM>> /etc/ld.so.conf by mistake. /usr/local/bin not in $PATH.
|
|
</EM><BR>
|
|
<EM>> Maybe I missed something but you don't mention the /etc/ld.so.conf
|
|
</EM><BR>
|
|
<EM>> thing. However, I'm pretty sure that at least for Debian potato this
|
|
</EM><BR>
|
|
<EM>> entry is absolutely necessary. Compiling xsane won't work without it.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> * I would be very careful with copying kernel headers to glibc
|
|
</EM><BR>
|
|
<EM>> directories. This may work for SANE but may break compilation of
|
|
</EM><BR>
|
|
<EM>> other programs using SCSI. And you probably won't remember that you
|
|
</EM><BR>
|
|
<EM>> changed /usr/include/scsi if these problems occur.
|
|
</EM><BR>
|
|
<EM>> Because this is for beginners, I would add that you
|
|
</EM><BR>
|
|
<EM>> need to have installed the kernel source or at least the kernel
|
|
</EM><BR>
|
|
<EM>> headers.
|
|
</EM><BR>
|
|
<EM>> What I did when having problems with different sg.h files in
|
|
</EM><BR>
|
|
<EM>> /usr/include and /usr/src/linux was to just rename sg.h to something
|
|
</EM><BR>
|
|
<EM>> else. Then the file in /usr/src/linux was used automatically.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> * Better write down that the permissions of /dev/sg0 must be rw for
|
|
</EM><BR>
|
|
<EM>> "other". At least I can't read the text in your file manager. If
|
|
</EM><BR>
|
|
<EM>> more than one person uses the system, I wouldn't do that however.
|
|
</EM><BR>
|
|
<EM>> Better set /dev/sg0 to rw for a group (e.g. "scanner") and add all
|
|
</EM><BR>
|
|
<EM>> the users that are allowed to scan to that group.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> * Why do you make the link to xsane (in the users ~/.gimp directory) as
|
|
</EM><BR>
|
|
<EM>> root? And be sure to mention that gimp shouldn't be run as root.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> * The "Special note: USB scanners" contains some unclear points and
|
|
</EM><BR>
|
|
<EM>> some mistakes in my opinion: The second sentence says to include the
|
|
</EM><BR>
|
|
<EM>> following line into modules.conf. The following line is "Model :
|
|
</EM><BR>
|
|
<EM>> Vendor ID : Product ID" :-).
|
|
</EM><BR>
|
|
<EM>> You are asking for vendor/product ids of other scanners. Maybe you
|
|
</EM><BR>
|
|
<EM>> want to link to <A HREF="http://www.linux-usb.org">http://www.linux-usb.org</A>, they have a list of such
|
|
</EM><BR>
|
|
<EM>> ids.
|
|
</EM><BR>
|
|
<EM>> You write that it's necessary to add "modprobe scanner vendor=<your
|
|
</EM><BR>
|
|
<EM>> vendor ID> product=<your product ID>" to modules.conf. However,
|
|
</EM><BR>
|
|
<EM>> modules.conf contains the options of the modules, not the modprobe
|
|
</EM><BR>
|
|
<EM>> itsself. So something like "options scanner vendor=<your vendor ID>
|
|
</EM><BR>
|
|
<EM>> product=<your product ID>" should work. By the way: In principle
|
|
</EM><BR>
|
|
<EM>> scanners should work without manually adding the ids, if they don't
|
|
</EM><BR>
|
|
<EM>> please send the necessary ids and the name of the scanner to the
|
|
</EM><BR>
|
|
<EM>> author of the scanner module for inclusion.
|
|
</EM><BR>
|
|
<EM>> Better add a warning that at least for Debian "modules.conf" shouldn't
|
|
</EM><BR>
|
|
<EM>> be changed manually. As the comment in this file says:
|
|
</EM><BR>
|
|
<EM>> # Please do not edit this file directly. If you want to change or add
|
|
</EM><BR>
|
|
<EM>> # anything please take a look at the files in /etc/modutils and read
|
|
</EM><BR>
|
|
<EM>> # the manpage for update-modules.
|
|
</EM><BR>
|
|
<EM>> Concerning *.conf when you don't use the epson backend: I'm not sure
|
|
</EM><BR>
|
|
<EM>> if every backend uses the "usb /dev/something" entry for *.conf. So
|
|
</EM><BR>
|
|
<EM>> better point to the documentation.
|
|
</EM><BR>
|
|
<EM>> After the paragraph about epson.conf you write "Mine looks like
|
|
</EM><BR>
|
|
<EM>> this: modprobe scanner vendor=0x04b8 product=ox010c". This should be
|
|
</EM><BR>
|
|
<EM>> moved to the paragraph about modules.conf (and exchange "modprobe" by
|
|
</EM><BR>
|
|
<EM>> "options"). The hex codes must start with 0x not ox.
|
|
</EM><BR>
|
|
<EM>> I would *not* add the link from /dev/usbscanner to /dev/scanner.
|
|
</EM><BR>
|
|
<EM>> /dev/scanner is used by all the SCSI backends and looking at USB
|
|
</EM><BR>
|
|
<EM>> device files as a SCSI generic file may cause havoc.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> Generally: For all things you need to do as root I would recommend to
|
|
</EM><BR>
|
|
<EM>> use something like 'su -c "make install"'. This way there is no risk to
|
|
</EM><BR>
|
|
<EM>> forget to "exit" the su shell.
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> Bye,
|
|
</EM><BR>
|
|
<EM>> Henning
|
|
</EM><BR>
|
|
<EM>>
|
|
</EM><BR>
|
|
<EM>> --
|
|
</EM><BR>
|
|
<EM>> Source code, list archive, and docs: <A HREF="http://www.mostang.com/sane/">http://www.mostang.com/sane/</A>
|
|
</EM><BR>
|
|
<EM>> To unsubscribe: echo unsubscribe sane-devel | mail <A HREF="mailto:majordomo@mostang.com?Subject=Re:%20./configure%20xsane%20is%20failing?&In-Reply-To=<01042102555000.00623@horche>">majordomo@mostang.com</A>
|
|
</EM><BR>
|
|
<P><PRE>
|
|
--
|
|
Source code, list archive, and docs: <A HREF="http://www.mostang.com/sane/">http://www.mostang.com/sane/</A>
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <A HREF="mailto:majordomo@mostang.com?Subject=Re:%20./configure%20xsane%20is%20failing?&In-Reply-To=<01042102555000.00623@horche>">majordomo@mostang.com</A>
|
|
</PRE>
|
|
<P><!-- body="end" -->
|
|
<HR NOSHADE>
|
|
<UL>
|
|
<!-- next="start" -->
|
|
<LI><STRONG>Next message:</STRONG> <A HREF="0212.html">Marcel Pol: "Microtek scanner not working anymore"</A>
|
|
<LI><STRONG>Previous message:</STRONG> <A HREF="0210.html">Onno Garms: "Snapscan 310 at Adaptec 1505 does not work"</A>
|
|
<LI><STRONG>In reply to:</STRONG> <A HREF="0196.html">Henning Meier-Geinitz: "Re: ./configure xsane is failing?"</A>
|
|
<!-- nextthread="start" -->
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0213.html">Henning Meier-Geinitz: "Re: ./configure xsane is failing?"</A>
|
|
<LI><STRONG>Next in thread:</STRONG> <A HREF="0195.html">Massimo Maiurana: "Re: ./configure xsane is failing?"</A>
|
|
<LI><STRONG>Reply:</STRONG> <A HREF="0213.html">Henning Meier-Geinitz: "Re: ./configure xsane is failing?"</A>
|
|
<!-- reply="end" -->
|
|
<LI><STRONG>Messages sorted by:</STRONG>
|
|
<A HREF="date.html#211">[ date ]</A>
|
|
<A HREF="index.html#211">[ thread ]</A>
|
|
<A HREF="subject.html#211">[ subject ]</A>
|
|
<A HREF="author.html#211">[ author ]</A>
|
|
</UL>
|
|
<!-- trailer="footer" -->
|
|
<HR NOSHADE>
|
|
<P>
|
|
<SMALL>
|
|
<EM>
|
|
This archive was generated by <A HREF="http://www.hypermail.org/">hypermail 2b29</A>
|
|
: <EM>Sat Apr 21 2001 - 11:26:16 PDT</EM>
|
|
</EM>
|
|
</SMALL>
|
|
</BODY>
|
|
</HTML>
|