From: Gerald Roth <gerald.roth@aon.at>
To: linux-kernel@vger.kernel.org
Subject: 2.4.18-rc2-aa1 compilation failure
Date: Thu, 21 Feb 2002 01:30:51 +0100 [thread overview]
Message-ID: <20020221003306Z292265-889+4243@vger.kernel.org> (raw)
make[3]: Entering directory `/usr/src/linux/fs/reiserfs'
make[3]: Circular /usr/src/linux/include/asm/pgalloc.h <-
/usr/src/linux/include/linux/highmem.h dependency dropped.
gcc -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=i686 -malign-functions=4
-DKBUILD_BASENAME=bitmap -c -o bitmap.o bitmap.c
bitmap.c: In function `reiserfs_free_prealloc_block':
bitmap.c:142: warning: unused variable `s'
gcc -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=i686 -malign-functions=4
-DKBUILD_BASENAME=do_balan -c -o do_balan.o do_balan.c
gcc -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=i686 -malign-functions=4
-DKBUILD_BASENAME=namei -c -o namei.o namei.c
gcc -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=i686 -malign-functions=4
-DKBUILD_BASENAME=inode -c -o inode.o inode.c
inode.c: In function `reiserfs_direct_io':
inode.c:2097: `filp' undeclared (first use in this function)
inode.c:2097: (Each undeclared identifier is reported only once
inode.c:2097: for each function it appears in.)
make[3]: *** [inode.o] Error 1
make[3]: Leaving directory `/usr/src/linux/fs/reiserfs'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux/fs/reiserfs'
make[1]: *** [_subdir_reiserfs] Error 2
make[1]: Leaving directory `/usr/src/linux/fs'
make: *** [_dir_fs] Error 2
hth
gerald
reply other threads:[~2002-02-21 0:33 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=20020221003306Z292265-889+4243@vger.kernel.org \
--to=gerald.roth@aon.at \
--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®