From: Arnvid Karstad <arnvid@karstad.org>
To: linux-kernel@vger.kernel.org
Subject: Problems compiling 2.4.7 with DAC960
Date: Mon, 30 Jul 2001 07:48:19 +0200 [thread overview]
Message-ID: <20010730073901.A59C.ARNVID@karstad.org> (raw)
Hiya,
I can't seem to be getting 2.4.7 to compile on one of our boxes.
I get this error:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.7/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DEXPORT_SYMTAB -c DAC960.c
DAC960.c: In function `DAC960_ProcessRequest':
DAC960.c:2771: structure has no member named `sem'
make[3]: *** [DAC960.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.7/drivers/block'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.7/drivers/block'
make[1]: *** [_subdir_block] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.7/drivers'
make: *** [_dir_drivers] Error 2
[root@x linux]#
I get the same error when trying to compile it as a module..
Is it broken, or is something else broken?
regards,
Arnvid Karstad
next reply other threads:[~2001-07-30 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 5:48 Arnvid Karstad [this message]
2001-07-30 6:31 ` Problems compiling 2.4.7 with DAC960 Jens Axboe
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=20010730073901.A59C.ARNVID@karstad.org \
--to=arnvid@karstad.org \
--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