From: Samuel Flory <sflory@rackable.com>
To: Atul.Mukker@lsil.com
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.23-pre7 Megaraid2 compile fails
Date: Mon, 20 Oct 2003 10:05:22 -0700 [thread overview]
Message-ID: <3F9415D2.7030900@rackable.com> (raw)
In-Reply-To: <3F9414C5.1060003@rackable.com>
Samuel Flory wrote:
> I'm not sure if anyone has reported this.
>
> gcc -D__KERNEL__ -I/stuff/src/linux-2.4.23-pre7/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
> -nostdinc -iwithprefix include -DKBUILD_BASENAME=megaraid2 -c -o
> megaraid2.o megaraid2.c
> megaraid2.c: In function `mega_find_card':
> megaraid2.c:403: structure has no member named `lock'
> make[3]: *** [megaraid2.o] Error 1
> make[3]: Leaving directory `/stuff/src/linux-2.4.23-pre7/drivers/scsi'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/stuff/src/linux-2.4.23-pre7/drivers/scsi'
> make[1]: *** [_subdir_scsi] Error 2
> make[1]: Leaving directory `/stuff/src/linux-2.4.23-pre7/drivers'
> make: *** [_dir_drivers] Error 2
>
>
> The driver does compile as a module, but not built into the kernel.
>
>
Actually it fails as module as well;-( Sorry I could swear I saw it
get past megaraid2.
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-10-20 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 17:00 2.4.23-pre7 Megaraid2 compile fails Samuel Flory
2003-10-20 17:05 ` Samuel Flory [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-20 17:48 Matt_Domsch
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=3F9415D2.7030900@rackable.com \
--to=sflory@rackable.com \
--cc=Atul.Mukker@lsil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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.