From: "Petter Sundlöf" <petter.sundlof@findus.dhs.org>
To: linux-kernel@vger.kernel.org
Subject: Voluntary Preempt P9 againstclean 2.6.8.1 -- on AMD64, compile failure
Date: Fri, 27 Aug 2004 19:12:20 +0200 [thread overview]
Message-ID: <412F6B74.5090806@findus.dhs.org> (raw)
On Debian-AMD64
Applied
http://redhat.com/~mingo/voluntary-preempt/voluntary-preempt-2.6.8.1-P9
to a clean 2.6.8.1 (simply copied over my old .config). Patching went
fine. Using gcc 3.3.4.
CC kernel/hardirq.o
kernel/hardirq.c: In function `recalculate_desc_flags':
kernel/hardirq.c:309: error: `SA_NODELAY' undeclared (first use in this
function)
kernel/hardirq.c:309: error: (Each undeclared identifier is reported
only once
kernel/hardirq.c:309: error: for each function it appears in.)
kernel/hardirq.c: In function `generic_setup_irq':
kernel/hardirq.c:339: error: `SA_NODELAY' undeclared (first use in this
function)
kernel/hardirq.c: In function `threaded_read_proc':
kernel/hardirq.c:641: error: `SA_NODELAY' undeclared (first use in this
function)
kernel/hardirq.c: In function `threaded_write_proc':
kernel/hardirq.c:659: error: `SA_NODELAY' undeclared (first use in this
function)
make[2]: *** [kernel/hardirq.o] Error 1
make[1]: *** [kernel] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.8.1'
make: *** [stamp-build] Error 2
Clean 2.6.8.1, patched with 2.6.8.1
Had to set CONFIG_VOLUNTARY_PREEMPT=y / CONFIG_PREEMPT_VOLUNTARY=y
manually in .config. I talked to a guy who said it was there in his
"menuconfig". For me the option didn't appear.
Here's my .config: http://findus.dhs.org/~odd/.config
Any idea?
gcc 3.3.4
Cheers.
next reply other threads:[~2004-08-27 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 17:12 Petter Sundlöf [this message]
[not found] <2xSys-7h8-11@gated-at.bofh.it>
2004-08-28 13:49 ` Voluntary Preempt P9 againstclean 2.6.8.1 -- on AMD64, compile failure Andi Kleen
2004-08-28 17:33 ` Petter Sundlöf
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=412F6B74.5090806@findus.dhs.org \
--to=petter.sundlof@findus.dhs.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