From: "Mike Black" <mblack@csihq.com>
To: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: 2.5.20 RAID5 compile error
Date: Mon, 3 Jun 2002 14:36:33 -0400 [thread overview]
Message-ID: <04cf01c20b2d$96097030$f6de11cc@black> (raw)
RAID5 still doesn't compile....sigh....
gcc -D__KERNEL__ -I/usr/src/linux-2.5.14/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-alias
ing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DKBUILD_BASENAME=raid5 -c -o raid5.o raid5.c
raid5.c: In function `raid5_plug_device':
raid5.c:1247: `tq_disk' undeclared (first use in this function)
raid5.c:1247: (Each undeclared identifier is reported only once
raid5.c:1247: for each function it appears in.)
raid5.c: In function `run':
raid5.c:1589: sizeof applied to an incomplete type
make[2]: *** [raid5.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.5.14/drivers/md'
make[1]: *** [_modsubdir_md] Error 2
make[1]: Leaving directory `/usr/src/linux-2.5.14/drivers'
make: *** [_mod_drivers] Error 2
Michael D. Black mblack@csihq.com
http://www.csihq.com/
http://www.csihq.com/~mike
321-676-2923, x203
Melbourne FL
next reply other threads:[~2002-06-03 18:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 18:36 Mike Black [this message]
2002-06-04 11:51 ` 2.5.20 RAID5 compile error Jens Axboe
2002-06-04 11:56 ` Neil Brown
2002-06-04 11:58 ` Jens Axboe
2002-06-04 12:15 ` Neil Brown
2002-06-04 12:21 ` Jens Axboe
2002-06-04 12:32 ` Jens Axboe
2002-06-04 12:38 ` Jens Axboe
2002-06-04 14:23 ` Jens Axboe
2002-06-04 13:45 ` Martin Dalecki
2002-06-04 14:55 ` Jens Axboe
2002-06-04 14:24 ` Martin Dalecki
2002-06-04 18:22 ` Horst von Brand
2002-06-05 10:19 ` Jens Axboe
2002-06-04 17:00 ` Ingo Oeser
2002-06-05 1:16 ` Neil Brown
2002-06-05 10:13 ` Jens Axboe
2002-06-06 2:58 ` Neil Brown
2002-06-06 5:31 ` Jens Axboe
2002-06-04 21:48 ` Miles Lane
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='04cf01c20b2d$96097030$f6de11cc@black' \
--to=mblack@csihq.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.