Re: [hpoj-devel] tonight's code changes

[Obi-Wan <bv...@in...>]

>> Close, but not quite.  In configure, line 801 uses -x to check for
>> libqt.so.
>
> You're pretty brave if you're reading the configure script.  :-)

I've been a Unix hacker (in the original sense of the word) for over
a decade.  Shell scripts are nothing.  'truss' and 'strace' are quickly
becoming my favorite tools for debugging 3rd party software.

>> That won't work on Debian because libqt.so is a symlink
>> to libqt.so.2.3.0 (or whatever version you have).  -x fails for
>> symlinks.  I changed it to -f and all is well.
>> 
>> # dir /usr/lib/libqt.so*
>> lrwxrwxrwx    1 root     root           14 May 31 01:06 /usr/lib/libqt.so -> libqt.so.2.3.0
>> lrwxrwxrwx    1 root     root           14 May 31 00:56 /usr/lib/libqt.so.2 -> libqt.so.2.3.0
>> lrwxrwxrwx    1 root     root           14 May 31 00:56 /usr/lib/libqt.so.2.3 -> libqt.so.2.3.0
>> -rw-r--r--    1 root     root      4943852 May 25 02:28 /usr/lib/libqt.so.2.3.0
> 
> That sounds like a bash bug to me, because it's a symlink on my system too
> and -x works fine.  According to the bash man page:
> -e file -- true if file exists.
> -f file -- true if file exists and is a regular file.
> -L file -- true if file exists and is a symbolic link.
> -x file -- true if file exists and is executable.
> Neither -f nor -x claim to either include or exclude symlinks.  Therefore,
> it seems to me that -e (the most permissive of all) would be a safer
> workaround to detect libqt.so.  Let me know if -e works for you, and I'll
> change it to that if it does.

OK, I was wrong in my earlier analysis.  -x follows symlinks just
fine.  However, shared libs don't have to be executable, and in my
case, it's not.  See the last line of the 'ls' output above.  -f
or !-z are probably the best ones to use, but use -e if you wish.

>> I seem to remember seeing somewhere when I was setting up all this
>> printing & scanning stuff that I should used the 2.2.x kernel instead
>> of the 2.4.x kernel.  Is that currently true?  Did it used to be true?
>
> That was true for previous released versions.  Even 0.7 ended up having
> trouble with some last-minute changes in 2.4, but there's a patch available
> to fix that.

But there are no problems with running the current CVS tree on 2.4.5,
right?  I'm currently running 2.2.16.  I want to start fiddling with
FireWire stuff for my camcorder, which prefers the newer kernels.

> I take it you haven't tried running
> "scanimage --test", because that has a tendency to lock up certain models,
> including yours.  I'm working on a fix for that problem right now.

No, I hadn't.  I ran it just now and it took 30 seconds to generate:

# scanimage --test
scanimage: scanning image of size 5096x7014 pixels at 1 bits/pixel
scanimage: acquiring gray frame, 1 bits/sample
scanimage: reading one scanline, 637 bytes...   PASS
scanimage: reading one byte...          PASS
scanimage: stepped read, 2 bytes...     PASS
scanimage: stepped read, 4 bytes...     PASS
scanimage: stepped read, 8 bytes...     PASS
scanimage: stepped read, 16 bytes...    PASS
scanimage: stepped read, 32 bytes...    PASS
scanimage: stepped read, 64 bytes...    PASS
scanimage: stepped read, 128 bytes...   PASS
scanimage: stepped read, 256 bytes...   PASS
scanimage: stepped read, 512 bytes...   PASS
scanimage: stepped read, 1024 bytes...  PASS
scanimage: stepped read, 1023 bytes...  PASS
scanimage: stepped read, 511 bytes...   PASS
scanimage: stepped read, 255 bytes...   PASS
scanimage: stepped read, 127 bytes...   PASS
scanimage: stepped read, 63 bytes...    PASS
scanimage: stepped read, 31 bytes...    PASS
scanimage: stepped read, 15 bytes...    PASS
scanimage: stepped read, 7 bytes...     PASS
scanimage: stepped read, 3 bytes...     PASS

Lest you balk at the time, remember that I'm running a K6-166 with 32MB RAM.

				-- Obi-Wan

-- 
Ben "Obi-Wan" Hollingsworth                             ob...@je...
   The stuff of earth competes for the allegiance I owe only to the
     Giver of all good things, so if I stand, let me stand on the
       promise that You will pull me through.  -- Rich Mullins