From: Zoltan NAGY <nagyz@nefty.hu>
To: linux-kernel@vger.kernel.org
Subject: 2.6.10-rc3-bk4 does not compile
Date: Thu, 09 Dec 2004 17:16:39 +0100 [thread overview]
Message-ID: <41B87A67.30803@nefty.hu> (raw)
It fails with the following error messages:
CC drivers/block/rd.o
drivers/block/rd.c:67: error: `CONFIG_BLK_DEV_RAM_COUNT' undeclared here
(not in a function)
drivers/block/rd.c:68: error: `CONFIG_BLK_DEV_RAM_COUNT' undeclared here
(not in a function)
drivers/block/rd.c:69: error: `CONFIG_BLK_DEV_RAM_COUNT' undeclared here
(not in a function)
drivers/block/rd.c: In function `rd_cleanup':
drivers/block/rd.c:403: error: `CONFIG_BLK_DEV_RAM_COUNT' undeclared
(first use in this function)
drivers/block/rd.c:403: error: (Each undeclared identifier is reported
only once
drivers/block/rd.c:403: error: for each function it appears in.)
drivers/block/rd.c: In function `rd_init':
drivers/block/rd.c:433: error: `CONFIG_BLK_DEV_RAM_COUNT' undeclared
(first use in this function)
drivers/block/rd.c: At top level:
drivers/block/rd.c:67: error: storage size of `rd_disks' isn't known
drivers/block/rd.c:68: error: storage size of `rd_bdev' isn't known
drivers/block/rd.c:69: error: storage size of `rd_queue' isn't known
drivers/block/rd.c:67: warning: `rd_disks' defined but not used
drivers/block/rd.c:68: warning: `rd_bdev' defined but not used
drivers/block/rd.c:69: warning: `rd_queue' defined but not used
make[2]: *** [drivers/block/rd.o] Error 1
make[1]: *** [drivers/block] Error 2
make: *** [drivers] Error 2
Regards,
Zoltan NAGY,
Software Engineer
next reply other threads:[~2004-12-09 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 16:16 Zoltan NAGY [this message]
2004-12-09 16:05 ` 2.6.10-rc3-bk4 does not compile Randy.Dunlap
2004-12-09 17:13 ` Zoltan NAGY
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=41B87A67.30803@nefty.hu \
--to=nagyz@nefty.hu \
--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.