From: Andrew Morton <akpm@osdl.org>
To: Patrick McLean <pmclean@cs.ubishops.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2-mm5 x86-64 link errors
Date: Thu, 7 Aug 2003 14:03:10 -0700 [thread overview]
Message-ID: <20030807140310.4e2c8a79.akpm@osdl.org> (raw)
In-Reply-To: <3F32AA2B.20809@cs.ubishops.ca>
Patrick McLean <pmclean@cs.ubishops.ca> wrote:
>
> I get to play with an opteron for a bit, so I'm going to try 2.6 on it,
> but test2-mm5 seems to compile fine, but when it goes to link it, it
> gives these errors:
>
> LD init/built-in.o
> LD .tmp_vmlinux1
> kernel/built-in.o(.text+0x359): In function `try_to_wake_up':
> : undefined reference to `sched_clock'
Ingo's scheduler patch requires that the architecture provide a
sched_clock() function which returns nanoseconds. We only have ia32, ia64,
ppc and ppc64 versions thus far.
A lame version is to just add
unsigned long long sched_clock(void)
{
return (unsigned long long)jiffies * (1000000000 / HZ);
}
to arch/<foo>/kernel/timer.c
prev parent reply other threads:[~2003-08-07 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 19:36 2.6.0-test2-mm5 x86-64 link errors Patrick McLean
2003-08-07 21:03 ` Andrew Morton [this message]
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=20030807140310.4e2c8a79.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmclean@cs.ubishops.ca \
/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