From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 566] New: compile failure in drivers/char/rio/rio_linux.c
Date: Wed, 09 Apr 2003 14:59:08 -0700 [thread overview]
Message-ID: <14680000.1049925548@flay> (raw)
http://bugme.osdl.org/show_bug.cgi?id=566
Summary: compile failure in drivers/char/rio/rio_linux.c
Kernel Version: 2.5.67
Status: NEW
Severity: low
Owner: rmk@arm.linux.org.uk
Submitter: john@larvalstage.com
Distribution: Gentoo 1.4rc2
Hardware Environment: Abit KG7-RAID, AMD AthlonXP 2100+, 512MB DDR
Software Environment: gcc 3.2.2, glibc 2.3.1, ld 2.13.90.0.18
Problem Description:
gcc -Wp,-MD,drivers/char/rio/.rio_linux.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe
-mpreferred-stack-boundary=2 -march=athlon -Iinclude/asm-i386/mach-default
-nostdinc -iwithprefix include -DKBUILD_BASENAME=rio_linux
-DKBUILD_MODNAME=rio -c -o drivers/char/rio/.tmp_rio_linux.o
drivers/char/rio/rio_linux.c
drivers/char/rio/rio_linux.c: In function `rio_ioctl':
drivers/char/rio/rio_linux.c:732: warning: implicit declaration of function
`verify_area'
drivers/char/rio/rio_linux.c:732: `VERIFY_READ' undeclared (first use in this
function)
drivers/char/rio/rio_linux.c:732: (Each undeclared identifier is reported only once
drivers/char/rio/rio_linux.c:732: for each function it appears in.)
drivers/char/rio/rio_linux.c:734: warning: implicit declaration of function
`get_user'
drivers/char/rio/rio_linux.c:741: `VERIFY_WRITE' undeclared (first use in this
function)
make[3]: *** [drivers/char/rio/rio_linux.o] Error 1
make[2]: *** [drivers/char/rio] Error 2
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2
Steps to reproduce:
Character devices --->
<*> Specialix RIO system support
CONFIG_RIO=y
reply other threads:[~2003-04-09 21:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=14680000.1049925548@flay \
--to=mbligh@aracnet.com \
--cc=linux-kernel@vger.kernel.org \
/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.