From: Kevin Brosius <cobra@compuserve.com>
To: kernel <linux-kernel@vger.kernel.org>
Subject: hugetlbpage.c build failure?
Date: Wed, 27 Nov 2002 17:28:18 -0500 [thread overview]
Message-ID: <3DE54702.44D98750@compuserve.com> (raw)
I see the following build failure in bk current:
gcc -Wp,-MD,arch/i386/mm/.hugetlbpage.o.d -D__KERNEL__ -Iinclude -Wall
-Wstric
t-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-po
inter -pipe -g -mpreferred-stack-boundary=2 -march=athlon
-Iarch/i386/mach-gener
ic -nostdinc -iwithprefix include -DKBUILD_BASENAME=hugetlbpage
-DKBUILD_MODN
AME=hugetlbpage -c -o arch/i386/mm/hugetlbpage.o
arch/i386/mm/hugetlbpage.c
arch/i386/mm/hugetlbpage.c:610: parse error before '*' token
arch/i386/mm/hugetlbpage.c: In function `hugetlb_sysctl_handler':
arch/i386/mm/hugetlbpage.c:611: number of arguments doesn't match
prototype
include/linux/hugetlb.h:14: prototype declaration
arch/i386/mm/hugetlbpage.c:612: warning: implicit declaration of
function `proc_
dointvec'
arch/i386/mm/hugetlbpage.c:612: `table' undeclared (first use in this
function)
arch/i386/mm/hugetlbpage.c:612: (Each undeclared identifier is reported
only onc
e
arch/i386/mm/hugetlbpage.c:612: for each function it appears in.)
arch/i386/mm/hugetlbpage.c:612: `write' undeclared (first use in this
function)
arch/i386/mm/hugetlbpage.c:612: `file' undeclared (first use in this
function)
arch/i386/mm/hugetlbpage.c:612: `buffer' undeclared (first use in this
function)
arch/i386/mm/hugetlbpage.c:612: `length' undeclared (first use in this
function)
make[1]: *** [arch/i386/mm/hugetlbpage.o] Error 1
make: *** [arch/i386/mm] Error 2
--
Kevin
next reply other threads:[~2002-11-27 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 22:28 Kevin Brosius [this message]
2002-11-27 22:44 ` hugetlbpage.c build failure? Greg KH
2002-11-28 0:58 ` Arnd Bergmann
2002-11-27 23:39 ` Kevin Brosius
2002-11-28 0:41 ` Greg KH
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=3DE54702.44D98750@compuserve.com \
--to=cobra@compuserve.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.