From: Bryce Harrington <bryce@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: 2.6.19-rc2-mm2 not building on ia64
Date: Fri, 20 Oct 2006 13:57:42 -0700 [thread overview]
Message-ID: <20061020205742.GU10386@osdl.org> (raw)
We're seeing the following error building the 2.6.19-rc2-mm2 kernel on
ia64 (it builds ok on x86_64). 2.6.19-rc2-git4 builds ok.
CC [M] drivers/acpi/processor_throttling.o
arch/ia64/sn/kernel/setup.c: In function `sn_setup':
arch/ia64/sn/kernel/setup.c:470: error: `ia64_timestamp_clock' undeclared (first use in this function)
arch/ia64/sn/kernel/setup.c:470: error: (Each undeclared identifier is reported only once
arch/ia64/sn/kernel/setup.c:470: error: for each function it appears in.)
CC fs/ext2/namei.o
make[2]: *** [arch/ia64/sn/kernel/setup.o] Error 1
make[1]: *** [arch/ia64/sn/kernel] Error 2
make: *** [arch/ia64/sn] Error 2
make: *** Waiting for unfinished jobs....
Full logs:
http://crucible.osdl.org/runs/2688/logs/ita01/kernel.config.log
http://crucible.osdl.org/runs/2688/logs/ita01/kernel.make.log
Config file:
http://crucible.osdl.org/runs/2688/sysinfo/ita01.config
Bryce
next reply other threads:[~2006-10-20 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 20:57 Bryce Harrington [this message]
2006-10-20 22:14 ` 2.6.19-rc2-mm2 not building on ia64 Jiri Kosina
2006-10-20 22:29 ` Andrew Morton
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=20061020205742.GU10386@osdl.org \
--to=bryce@osdl.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