Hi,
the warnings are a good tool to discover problems during development.
Reducing the number of warnings can be a good idea. But this depends on
the type of warning.
Some of them could only be solved by adding dummy code ("unused
parameter" in functions called through arrays of pointers to functi
Hi,
On Wed, Oct 10, 2001 at 12:44:40PM +0200, Joachim Backes wrote:
> But I think, it would be reasonable if one could select the available
> scanner(s) during ./configure, for example:
>
> ./configure --with-backend=epson,microtek2
>
> for example.
We have discussed this two or three t
Hi,
On Wed, Oct 10, 2001 at 08:30:49AM +0200, Jaeger, Gerhard wrote:
> shouldn't we try to fix these warnings prior to the next release???
Yes, that's the reason why I posted the list of warnings :-)
> If you compile a Linux kernel there are some warnings but not as much as
> 675... and this is
Everyone,
This morning it was brought to my attention that the
Umax Astra 1220U WikiWeb on SourceForge had
"disappeared".
I had made it a point to dump the contents of the
WikiWeb periodically so I could recover it it case
someone on the outside vandalized it, but those
backups are gone too.
The
Hi,
sorry for the late answer ...
> Now, after I installed SuSE 7.2 from scratch, I'm
> not able to get the scanner work again, trying with
> SANE Version 1.0.5.
> It ends up with an "Error during device I/O".
You should try to disable the "Quality calibration" option in xsane (or
xscanimage).
On 10-Oct-2001 Wolfgang Cohrs wrote:
> Joachim Backes wrote:
>
> > Hi,
> >
> > I have a question: is it possible to configure sane-backends
> > only for _one_ scanner type (with omitting all others which
> > are not needed), and therefore to compile it in a shorter
> > time (similar to a specif
Joachim Backes wrote:
> Hi,
>
> I have a question: is it possible to configure sane-backends
> only for _one_ scanner type (with omitting all others which
> are not needed), and therefore to compile it in a shorter
> time (similar to a specific configured linux kernel)?
>
> Regards
>
> Joachim Bac
Hi,
I have a question: is it possible to configure sane-backends
only for _one_ scanner type (with omitting all others which
are not needed), and therefore to compile it in a shorter
time (similar to a specific configured linux kernel)?
Regards
Joachim Backes
--
Joachim Backes| Univ. o
On Dienstag, 9. Oktober 2001 22:21, Henning Meier-Geinitz wrote:
> Hi,
>
> Compiling SANE still results in lots of warnings (ca. 675). Here are
> some statistics:
>
> Warnings sorted by backend (./configure --enable-warnings, on a
> linux/gcc system):
[SNIP-SNAP]
Hi list,
shouldn't we try to fix
