From: Jiri Slaby <jslaby@suse.cz>
To: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: ia64 build broken on CONFIG_DEBUG_STACK_USAGE
Date: Mon, 22 Aug 2011 09:27:31 +0200 [thread overview]
Message-ID: <4E5204E3.7070107@suse.cz> (raw)
Hi,
when CONFIG_DEBUG_STACK_USAGE is selected, I get these errors:
CC arch/ia64/kernel/asm-offsets.s
In file included from arch/ia64/kernel/asm-offsets.c:9:
include/linux/sched.h: In function ‘stack_not_used’:
include/linux/sched.h:2419: error: ‘IA64_TASK_SIZE’ undeclared (first
use in this function)
include/linux/sched.h:2419: error: (Each undeclared identifier is
reported only once
include/linux/sched.h:2419: error: for each function it appears in.)
include/linux/sched.h:2419: error: ‘IA64_THREAD_INFO_SIZE’ undeclared
(first use in this function)
make[1]: *** [arch/ia64/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2
regards,
--
js
suse labs
next reply other threads:[~2011-08-22 7:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 7:27 Jiri Slaby [this message]
2011-09-16 21:20 ` ia64 build broken on CONFIG_DEBUG_STACK_USAGE Jiri Slaby
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=4E5204E3.7070107@suse.cz \
--to=jslaby@suse.cz \
--cc=fenghua.yu@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox