On 6/6/07, Robin Stewart <s48264 at bluebottle.com> wrote: > > The above comments are in response to m. allan noah's email of 06/06/07 > 00:29 as quoted below: > > > > 1. downloading and extracting the sane source code > 2. downloading and possibly extracting rene's updated files > 3. replacing some files in the sane tarball with those from rene > 4. configure sane with the proper arguments to overwrite that provided > by your os > 5. make && make install
> you need to determine where your existing compilation of sane has > installed its files, and pass the correct arguments to ./configure to > use the same locations. this will overwrite the originals instead of > installing a second copy (which causes issues generally). run > configure with the --help option for more info. > > basically, we want to overwrite the scanimage and sane-find-scanner > programs, (probably in /usr/bin), the saned daemon program (probably > in /usr/sbin) as well as libsane.so.* and the sane/libsane-* libraries > (probably in /usr/lib). we also want to overwrite /etc/sane.d > > probably something like: > > ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var > > I am using 32 bit ubuntu. > The string above does not work for me at the moment. I think because I do > not know where to place it. > > I have put the sane source code as updated by Rene's coding in > > /home/robin/download/Sane Backends/sane-backends-1.0.18 > > Assuming that the installed versions of sane backends are as stated above by > you. Opening terminal which folder should I cd to run your configure string > above? > it is a command, which you must run while you are in the sane-backends-1.0.18 dir, except that it should have only had one dot before /confgure, i think i mis-typed it before. you might find 'cd' a little difficult to use since you put a space in one of the dir names. you might want to rename that. its a unix-ism you'll get used to... allan -- "The truth is an offense, but not a sin"
