From: Corporal Pisang <Corporal_Pisang@Counter-Strike.com.my>
To: linux-kernel@vger.kernel.org
Subject: 2.5.39 compile error (intermezzo)
Date: Mon, 30 Sep 2002 13:55:49 +0800 [thread overview]
Message-ID: <20020930135549.05a8ec4a.Corporal_Pisang@Counter-Strike.com.my> (raw)
Hi,
Another compile error
make[2]: Entering directory `/usr/src/linux/fs/intermezzo'
gcc -Wp,-MD,./.vfs.o.d -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=athlon -I/usr/src/linux/arch/i386/mach-generic -nostdinc -iwithprefix include -DMODULE -include /usr/src/linux/include/linux/modversions.h -DKBUILD_BASENAME=vfs -c -o vfs.o vfs.c
vfs.c: In function `presto_debug_fail_blkdev':
vfs.c:134: invalid initializer
vfs.c:136: warning: implicit declaration of function `is_read_only'
vfs.c: In function `presto_do_rmdir':
vfs.c:1244: warning: implicit declaration of function `double_down'
vfs.c:1260: warning: implicit declaration of function `double_up'
vfs.c: In function `presto_rename_dir':
vfs.c:1627: warning: implicit declaration of function `triple_down'
vfs.c:1644: warning: implicit declaration of function `triple_up'
vfs.c: In function `lento_do_rename':
vfs.c:1755: warning: implicit declaration of function `double_lock'
vfs.c: In function `lento_iopen':
vfs.c:1934: called object is not a function
vfs.c:1935: parse error before string constant
make[2]: *** [vfs.o] Error 1
make[2]: Leaving directory `/usr/src/linux/fs/intermezzo'
make[1]: *** [intermezzo] Error 2
make[1]: Leaving directory `/usr/src/linux/fs'
make: *** [fs] Error 2
Regards,
-Ubaida-
reply other threads:[~2002-09-30 5:40 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=20020930135549.05a8ec4a.Corporal_Pisang@Counter-Strike.com.my \
--to=corporal_pisang@counter-strike.com.my \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®