From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Giuseppe <gdm84@vodafone.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: can't compile udf
Date: Fri, 24 Oct 2003 12:14:26 -0700 [thread overview]
Message-ID: <20031024121426.12872b42.rddunlap@osdl.org> (raw)
In-Reply-To: <200310241256.42888.gdm84@vodafone.it>
On Fri, 24 Oct 2003 12:56:42 +0000 Giuseppe <gdm84@vodafone.it> wrote:
| I can't compile udf filesystem support with 2.6-test8 (i compiled it in
| test6); this is what i get:
|
| CC fs/udf/super.o
| fs/udf/super.c: In function `udf_parse_options':
| fs/udf/super.c:327: `opt' undeclared (first use in this function)
| fs/udf/super.c:327: (Each undeclared identifier is reported only once
| fs/udf/super.c:327: for each function it appears in.)
| fs/udf/super.c:332: `val' undeclared (first use in this function)
| fs/udf/super.c:310: warning: unused variable `p'
| fs/udf/super.c:311: warning: unused variable `option'
| fs/udf/udf_i.h: At top level:
| fs/udf/super.c:282: warning: `tokens' defined but not used
| make[2]: *** [fs/udf/super.o] Error 1
|
| I tried to compile it as a module and inside the kernel too. Please help me!
It looks like you have a confuzed source file. Did you download the
kernel tarball or apply bk patches or apply cvs patches or what?
These errors make no sense for 2.6.0-test8. The messages are not
correct for that kernel version.
Also, I have built it successfully.
If you continue to have these errors after checking the source file,
please send me your .config file.
Maybe compare your fs/udf/super.c file to the one here:
http://linus.bkbits.net:8080/linux-2.5/anno/fs/udf/super.c@1.37?nav=index.html|src/|src/fs|src/fs/udf
--
~Randy
prev parent reply other threads:[~2003-10-24 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-24 12:56 Giuseppe
2003-10-24 19:14 ` Randy.Dunlap [this message]
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=20031024121426.12872b42.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=gdm84@vodafone.it \
--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®