From: Mike Fedyk <mfedyk@matchmail.com>
To: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Compile problem with CONFIG_X86_CYCLONE_TIMER Re: 2.6.0-test3-mm2
Date: Fri, 15 Aug 2003 13:36:20 -0700 [thread overview]
Message-ID: <20030815203620.GO1027@matchmail.com> (raw)
In-Reply-To: <20030815202322.GN1027@matchmail.com>
On Fri, Aug 15, 2003 at 01:23:22PM -0700, Mike Fedyk wrote:
> On Fri, Aug 15, 2003 at 12:38:34PM -0700, Mike Fedyk wrote:
> > arch/i386/kernel/timers/timer_cyclone.c: In function `init_cyclone':
> > arch/i386/kernel/timers/timer_cyclone.c:157: `FIX_CYCLONE_TIMER' undeclared (first use in this function)
> > arch/i386/kernel/timers/timer_cyclone.c:157: (Each undeclared identifier is reported only once
> > arch/i386/kernel/timers/timer_cyclone.c:157: for each function it appears in.)
> > make[3]: *** [arch/i386/kernel/timers/timer_cyclone.o] Error 1
> > make[2]: *** [arch/i386/kernel/timers] Error 2
> > make[1]: *** [arch/i386/kernel] Error 2
> > make[1]: Leaving directory `/src/linux-2.6.0-test3-mm2'
> > make: *** [stamp-build] Error 2
> > Command exited with non-zero status 2
> > Command being timed: "fakeroot make-kpkg kernel_image"
> > User time (seconds): 61.96
> > System time (seconds): 13.53
> > Percent of CPU this job got: 76%
> > Elapsed (wall clock) time (h:mm:ss or m:ss): 1:38.10
> > Average shared text size (kbytes): 0
> > Average unshared data size (kbytes): 0
> > Average stack size (kbytes): 0
> > Average total size (kbytes): 0
> > Maximum resident set size (kbytes): 0
> > Average resident set size (kbytes): 0
> > Major (requiring I/O) page faults: 293436
> > Minor (reclaiming a frame) page faults: 143725
> > Voluntary context switches: 0
> > Involuntary context switches: 0
> > Swaps: 0
> > File system inputs: 0
> > File system outputs: 0
> > Socket messages sent: 0
> > Socket messages received: 0
> > Signals delivered: 0
> > Page size (bytes): 4096
> > Exit status: 2
> >
>
> I thought it might have been a problem with my kernel tree, but after
> untarring and patching to 2.6.0-test3-mm2, it is still giving the problem.
>
It depends on CONFIG_X86_GENERICARCH, so once that's not set, then
CONFIG_X86_CYCLONE_TIMER is not set either.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-08-15 20:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 8:31 2.6.0-test3-mm2 Andrew Morton
2003-08-13 13:02 ` 2.6.0-test3-mm2 Con Kolivas
2003-08-13 13:35 ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-13 13:36 ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-13 14:32 ` 2.6.0-test3-mm2 Hugh Dickins
2003-08-13 16:16 ` 2.6.0-test3-mm2 Martin J. Bligh
2003-08-13 16:18 ` 2.6.0-test3-mm2 Luiz Capitulino
2003-08-15 19:38 ` Compile problem with CONFIG_X86_CYCLONE_TIMER 2.6.0-test3-mm2 Mike Fedyk
2003-08-15 20:23 ` Mike Fedyk
2003-08-15 20:36 ` Mike Fedyk [this message]
2003-08-16 20:32 ` Dave Hansen
2003-08-27 1:08 ` Compile problem with CONFIG_X86_CYCLONE_TIMER Re: 2.6.0-test4-mm1 Mike Fedyk
2003-08-27 4:41 ` Dave Hansen
2003-08-27 16:00 ` Mike Fedyk
2003-08-27 16:15 ` Dave Hansen
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=20030815203620.GO1027@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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