From: "ismail dönmez" <ismail.donmez@gmail.com>
To: James Purser <purserj@ksit.dynalias.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Compile error on microtek.c in drivers/usb/image/
Date: Sat, 23 Apr 2005 09:16:52 +0300 [thread overview]
Message-ID: <2a4f155d05042223167d0db353@mail.gmail.com> (raw)
In-Reply-To: <1114234140.3074.6.camel@kryten>
Looks like its fixed already.See http://lkml.org/lkml/2005/4/21/247
ismail
On 4/23/05, James Purser <purserj@ksit.dynalias.com> wrote:
> When compiling from the git archive ran across this error, I changed the
> offending FAILUR to FAILED and it compiled fine, however not knowing the
> ins and outs, Im not sure if this is going to fix the problem.
>
> System: Fedora Core 2
> Compiler: gcc-3.3.3 (Redhat Version)
>
> drivers/usb/image/microtek.c: In function `mts_scsi_abort':
> drivers/usb/image/microtek.c:338: error: `FAILURE' undeclared (first use
> in this function)
> drivers/usb/image/microtek.c:338: error: (Each undeclared identifier is
> reported only once
> drivers/usb/image/microtek.c:338: error: for each function it appears
> in.)
> make[3]: *** [drivers/usb/image/microtek.o] Error 1
> make[2]: *** [drivers/usb/image] Error 2
> make[1]: *** [drivers/usb] Error 2
> make: *** [drivers] Error 2
>
>
> --
> James Purser
> http://ksit.dynalias.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Time is what you make of it
next prev parent reply other threads:[~2005-04-23 6:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 5:29 Compile error on microtek.c in drivers/usb/image/ James Purser
2005-04-23 6:16 ` ismail dönmez [this message]
2005-04-23 7:01 ` James Purser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2a4f155d05042223167d0db353@mail.gmail.com \
--to=ismail.donmez@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=purserj@ksit.dynalias.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.