From: Adrian Bunk <bunk@fs.tum.de>
To: Eduard Roccatello <lilo.please.no.spam@roccatello.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: p4-clockmod does not compile under 2.6.1-mm3
Date: Sat, 17 Jan 2004 01:41:13 +0100 [thread overview]
Message-ID: <20040117004112.GB12027@fs.tum.de> (raw)
In-Reply-To: <200401162014.24567.lilo.please.no.spam@roccatello.it>
On Fri, Jan 16, 2004 at 08:14:24PM +0100, Eduard Roccatello wrote:
> Hello :-)
Hi Eduard,
> bash-2.05b# gcc --version
> gcc (GCC) 3.2.3
>
> bash-2.05b# make
> SPLIT include/linux/autoconf.h -> include/config/*
> make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
> CHK include/linux/compile.h
> CC arch/i386/kernel/cpu/cpufreq/p4-clockmod.o
> arch/i386/kernel/cpu/cpufreq/p4-clockmod.c: In function `cpufreq_p4_setdc':
> arch/i386/kernel/cpu/cpufreq/p4-clockmod.c:71: `cpu_sibling_map' undeclared
> (first use in this function)
> arch/i386/kernel/cpu/cpufreq/p4-clockmod.c:71: (Each undeclared identifier
> is reported only once
> arch/i386/kernel/cpu/cpufreq/p4-clockmod.c:71: for each function it appears
> in.)
> make[3]: *** [arch/i386/kernel/cpu/cpufreq/p4-clockmod.o] Error 1
> make[2]: *** [arch/i386/kernel/cpu/cpufreq] Error 2
> make[1]: *** [arch/i386/kernel/cpu] Error 2
> make: *** [arch/i386/kernel] Error 2
>
> adding a cpumask_t cpu_sibling_map[NR_CPUS] to the function make it compile
> but i think this is a very bad solution (sorry I'm not a kernel hacker :-)
thanks for your report.
This was a known bug in -mm3 that is already fixed in -mm4 [1].
> Thanks,
> Eduard
cu
Adrian
[1] ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/broken-out/p4-clockmod-sibling-map-fix.patch
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-01-17 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 19:14 Eduard Roccatello
2004-01-17 0:41 ` Adrian Bunk [this message]
2004-01-16 22:47 Daniel Kirsten
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=20040117004112.GB12027@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=lilo.please.no.spam@roccatello.it \
--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
all inboxes | Powered by JetHome®