[sane-devel] RE: CONFIG_USB_SUSPEND and black scans

Hi Gerhard-- Could you tell me what are your versions of libusb & libsane? I have a report that libsane 1.0.19-cvs20070421-1 will not work, but libsane 1.0.18-6 will & I have a non-working with libusb 2:0.1.12-7 Dean > Message: 4 > Date: Mon, 7 May 2007 11:49:12 +0200 > From: Gerhard Jaeger

[sane-devel] Avision Backend

Allan It is not that I can not read carefully, but that I had found that the su command could not be run due to my only password being rejected. I therefore hoped that sudo would do and that is why I spelt out that I had used sudo not su. I had been given advice to use sudo in another situati

[sane-devel] RE: CONFIG_USB_SUSPEND and black scans

On Dienstag, 8. Mai 2007, Dean Loros wrote: > Hi Gerhard-- > > Could you tell me what are your versions of libusb & libsane? I have a > report that libsane 1.0.19-cvs20070421-1 will not work, but libsane > 1.0.18-6 will & I have a non-working with libusb 2:0.1.12-7 > Hi, I've installed libusb

[sane-devel] [ANNOUNCE] New SANE backend 'hp5590' for HP ScanJet 5550/5590/7650

On 5/6/07, Julien BLACHE wrote: > That's a question for Ilia ;) I think he did test everything as he has > the hardware, though. > The backend doesn't support scanning at 150 dpi yet, as its functionality is similar to Windows driver, which uses only limited list of scanner resolutions, doing its

[sane-devel] minor problem with current (20070507) CVS code on OS/2

On 5/8/07, Franz Bakan wrote: > configure (generated by Autoconf 2.61) fails and claims > not to find grep (which is bogus) > > Running autoconf (2.59) locally solves the problem. > > can someone please regenerate configure in cvs with autoconf 2.59 Please send the fragment of config.log from co

[sane-devel] Scanners available for experiments

Hi, I have some scanners lying around, and reading http://www.meier-geinitz.de/sane/misc/mustek-scanners.html#UNSUPPORTED and the referenced mailinglist entry http://lists.alioth.debian.org/pipermail/sane-devel/2004-August/011685.html I realized that instead of simply throwing out these scanners t

[sane-devel] Avision Backend

On 5/8/07, Robin Stewart wrote: > I appreciate you support and I am trying to follow your instructions but > at the time I could not do so because I did not know how to access the > root with the passwords that I remembered. if you intend to admin a unix or unix-like machine of any type, you MUST

[sane-devel] [ANNOUNCE] New SANE backend 'hp5590' for HP ScanJet 5550/5590/7650

On 5/8/07, Dale Amon wrote: > Do you have any idea why it would eject two pages > after it scans one? The scanner in question is rather high level in terms of commands, that means that I couldn't (at least, I didn't see such a possibility from the traces on Windows) say 'feed the next page into

[sane-devel] [RFC] On libsane symbols visibility

Doing native Win32 porting and new backend adding I ran into the question about libsane symbols visibility. That's what 'make libcheck' checks. Current libsane model (or better to say, programming conventions) don't allow to export unnecessary symbols from libsane libraries. That's wise because of

[sane-devel] Scanners available for experiments

Am Dienstag, den 08.05.2007, 13:52 +0200 schrieb Jonas Smedegaard: > > > Tell me if it is of any interest. > > > Heidelberg Linoscan 1200 (SCSI) > This scanner may be compatible to the umax backend. When you tell me the scsi id of the scanner and you are able to compile sane-backends from s

[sane-devel] [RFC] On libsane symbols visibility

"Ilia Sotnikov" wrote: > My suggestion is to mark the functions which are part of SANE API as > exportable (__attribute__ ((visibility("default"))) symbol attribute > and its companion, -fvisibility=hidden). It will give us the necessary > result - only explicitly marked symbols will be visible.

[sane-devel] [RFC] On libsane symbols visibility

On 5/8/07, Julien BLACHE wrote: > SANE traditionally builds with non-gcc compilers too, so this is kind > of a no-go for the gcc-deprived (or the gcc-sucks-no-way-I-use-it, > YMMV) :) > Then for such compilers we'll definitely need to use some #ifdef's. > Backends that use multiple files usually

[sane-devel] [RFC] On libsane symbols visibility

"Ilia Sotnikov" wrote: > Yes, I saw and used that solution. What about marking symbols > explicitly when compiling under native Windows and use no attributes > under other platforms? Otherwise we'll need to leave with > not-intended-to-but-exported symbols at least under Windows having > 'make li

[sane-devel] minor problem with current (20070507) CVS code on OS/2

On Tue, 8 May 2007 11:05:44 +0300, Ilia Sotnikov wrote: > > configure (generated by Autoconf 2.61) fails and claims > > not to find grep (which is bogus) > > > > Running autoconf (2.59) locally solves the problem. > > > > can someone please regenerate configure in cvs with autoconf 2.59 > > Plea

[sane-devel] [RFC] On libsane symbols visibility

On 5/8/07, Julien BLACHE wrote: > "Ilia Sotnikov" wrote: > > I don't know if a clean libcheck is mandatory/enforced as far as > native win32 is concerned; I think it can't be avoided if part of the > portable function library is used. As far as I understand, it's not enforced, but highly recomme

[sane-devel] [RFC] On libsane symbols visibility

"Ilia Sotnikov" wrote: > As far as I understand, it's not enforced, but highly recommended/good > coding style. Although, if hiding some symbols would introduce a lot > of portability problems, it should be avoided, in my opinion. > > Deciscion: don't introduce additional complexities and let som

[sane-devel] Scanners available for experiments

On Tue, 2007-05-08 at 13:52 +0200, Jonas Smedegaard wrote: > Hi, > > I have some scanners lying around, and reading > http://www.meier-geinitz.de/sane/misc/mustek-scanners.html#UNSUPPORTED > and the referenced mailinglist entry > http://lists.alioth.debian.org/pipermail/sane-devel/2004-August/0116

[sane-devel] [RFC] On libsane symbols visibility

On Tuesday 08 May 2007 16:15:38 Julien BLACHE wrote: > SANE traditionally builds with non-gcc compilers too, so this > is kind of a no-go for the gcc-deprived (or the > gcc-sucks-no-way-I-use-it, YMMV) :) Intel compiler version 9 supports these "-fvisibility" compiler options, on Mac and Linux, I

[sane-devel] [RFC] On libsane symbols visibility

I wish I can find the way to remove my address from the list without giving the pass word Thanks for help francesco --- William Gallafent wrote: > On Tuesday 08 May 2007 16:15:38 Julien BLACHE wrote: > > SANE traditionally builds with non-gcc compilers > too, so this > > is kind of a no-go for th

[sane-devel] [RFC] On libsane symbols visibility

I wish I can find the way to remove my address from the list without giving the pass word Thanks for help francesco --- Ilia Sotnikov wrote: > On 5/8/07, Julien BLACHE wrote: > > "Ilia Sotnikov" wrote: > > > > I don't know if a clean libcheck is > mandatory/enforced as far as > > native win32 i

[sane-devel] [RFC] On libsane symbols visibility

Francesco Pietra wrote: Hi, > I wish I can find the way to remove my address from > the list without giving the pass word > Thanks for help I've removed your address from the sane-devel mailing-list. JB. -- Julien BLACHE