From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: "list, linux-kernel" <linux-kernel@vger.kernel.org>,
"Tosatti, Marcelo" <marcelo@conectiva.com.br>
Subject: 2.4.23-pre7 build problems
Date: Fri, 10 Oct 2003 21:45:24 +1000 [thread overview]
Message-ID: <3F869BD4.ADB4D648@eyal.emu.id.au> (raw)
I dropped off the list for a few days so am not sure what was already
reported, neither did I find anything in the archives about -pre7.
already reported:
gcc -D__KERNEL__ -I/data2/usr/local/src/linux-2.4-pre/include -Wall
-Wstrict-pro
totypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer
-pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4
-DMODULE -DM
ODVERSIONS -include
/data2/usr/local/src/linux-2.4-pre/include/linux/modversions
.h -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[2]: *** [megaraid2.o] Error 1
make[2]: Leaving directory
`/data2/usr/local/src/linux-2.4-pre/drivers/scsi'
no report found:
gcc -D__KERNEL__ -I/data2/usr/local/src/linux-2.4-pre/include -Wall
-Wstrict-pro
totypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer
-pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4
-DMODULE -DM
ODVERSIONS -include
/data2/usr/local/src/linux-2.4-pre/include/linux/modversions
.h -nostdinc -iwithprefix include -DKBUILD_BASENAME=nsp32 -c -o
nsp32.o nsp32.
c
In file included from nsp32.c:56:
nsp32.h:645: redefinition of `irqreturn_t'
/data2/usr/local/src/linux-2.4-pre/include/linux/interrupt.h:16:
`irqreturn_t' previously declared here
make[2]: *** [nsp32.o] Error 1
make[2]: Leaving directory
`/data2/usr/local/src/linux-2.4-pre/drivers/scsi'
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
next reply other threads:[~2003-10-10 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 11:45 Eyal Lebedinsky [this message]
2003-10-10 12:48 ` Willy Tarreau
2003-10-11 14:47 ` Marcelo Tosatti
2003-10-11 15:13 ` 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=3F869BD4.ADB4D648@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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®