Le lundi 19 octobre 2009 ? 22:34 -0700, Adrian Sandor a ?crit :
> > > Well, you didn't say how.
> > You didn't ask for help ;-)
>
> Yes I did, I wrote "Anyway, please let me know when I can try the new code
> **and how**."
> But it's ok now.
Ok, misunderstanding of "how", thought you had already
On Sun, 2009-10-18 at 13:36 +0200, Nicolas Martin wrote:
>
> Louis:
> if the network support fails, I'm just wondering whether the DES name
> for this model is set correctly, the usb signature (from the USB snoop)
> was reported to be: "Canon MF4360-4390" so a bit different from what
> was seen
if you wish to set an environment variable before running a program,
you must either export that variable, or you must put it on the same
line:
SANE_DEBUG_GENESYS=255 scanimage -L
let us see what that produces.
allan
On Sat, Oct 17, 2009 at 8:41 PM, wrote:
> Hello,
> I am a complete newbie us
Hi,
@allan: I do not run xsane on the same mashine like the sane-server, so I do
not understand how to write the log you want me to.
"xsane... 2>net.log"
sanimage on the mashine where the sane-server runs, works fine.
@Olaf:"Compile the backend with gcc -Wall -Werror should give a cluebat." What
On Tue, Oct 20, 2009 at 2:49 AM, wrote:
> Hi,
>
> @allan: I do not run xsane on the same mashine like the sane-server, so I do
> not understand how to write the log you want me to.
> "xsane... 2>net.log"
easy, open a terminal window on the scanning client, and run the
command i gave you.
> san
"m. allan noah" writes:
> I had a similar problem with the fujitsu backend when I built 1.0.20
> on the slug a few months ago. The cross-compiler does not init vars to
> 0.
Eh, if you don't tell it to do so, yes. Using variables before
initialisation has been undefined behaviour since as long a
