From: "Oliver Pitzeier" <o.pitzeier@uptime.at>
To: 'Balint Cristian' <rezso@rdsor.ro>,
'Falk Hueffner' <falk.hueffner@student.uni-tuebingen.de>,
'Paolo Dovera' <pdovera@bmind.it>
Cc: linux-alpha@vger.kernel.org
Subject: RE: linux-2.6.0-test6 error during linking
Date: Mon, 29 Sep 2003 11:06:46 +0200 [thread overview]
Message-ID: <000901c38669$031d3640$020b10ac@pitzeier.priv.at> (raw)
In-Reply-To: <200309291148.14567.rezso@rdsor.ro>
> On Sunday 28 September 2003 23:51, Falk Hueffner wrote:
> > Paolo Dovera <pdovera@bmind.it> writes:
> > > Applied patch-2.6.0-test6 I receive the following error:
> > >
> > > kernel/built-in.o(.text+0x5068): In function `copy_process':
> > > : undefined reference to `sched_clock'
> > >
> > > kernel/built-in.o(.text+0x506c): more undefined references to
> > > `sched_clock' follow
> >
> > sched_clock is not implemented yet for Alpha. It is
> supposed to return
> > a high resolution timer. As workaround, you could just copy the
> > implementation from ARM, which simply returns the value based on
> > jiffies. Ideally, one would take into account the cycle
> counter, but
> > it wraps every few seconds, which has to be taken care of.
>
> Can post here a patch based on arm ?
>
> I am courious to see it !
>
> Eventualy post it on linux kernel list or to Richard Henderson ?
>
> Thx a lot !
Please take a look at the LKML. I had the same problem with -test6 and viro
already posted a workaround!
Best,
Oliver
prev parent reply other threads:[~2003-09-29 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-28 19:55 linux-2.6.0-test6 error during linking Paolo Dovera
2003-09-28 20:51 ` Falk Hueffner
2003-09-29 8:48 ` Balint Cristian
2003-09-29 9:02 ` Falk Hueffner
2003-09-29 9:05 ` Balint Cristian
2003-09-29 18:05 ` Paolo Dovera
2003-09-29 9:06 ` Oliver Pitzeier [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='000901c38669$031d3640$020b10ac@pitzeier.priv.at' \
--to=o.pitzeier@uptime.at \
--cc=falk.hueffner@student.uni-tuebingen.de \
--cc=linux-alpha@vger.kernel.org \
--cc=pdovera@bmind.it \
--cc=rezso@rdsor.ro \
/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;
as well as URLs for NNTP newsgroup(s).