From: Adrian Bunk <bunk@fs.tum.de>
To: Robert F Merrill <griever@t2n.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.2-mm1 won't compile (been doing this since 2.6.1-mm2 or so)
Date: Sat, 7 Feb 2004 22:36:46 +0100 [thread overview]
Message-ID: <20040207213646.GE7388@fs.tum.de> (raw)
In-Reply-To: <402558C0.5010100@t2n.org>
On Sat, Feb 07, 2004 at 04:29:36PM -0500, Robert F Merrill wrote:
> When I upgraded to 2.6.1-mm4, I did the usual thing, copied my old
> .config from 2.6.1-mm1 and did make oldconfig.
>
> However, when I run make, this happens:
>
> include/asm/processor.h:68: error: `CONFIG_X86_L1_CACHE_SHIFT'
> undeclared here (not in a function)
> include/asm/processor.h:68: error: requested alignment is not a constant
> make[1]: *** [arch/i386/kernel/asm-offsets.s] Error 1
>
>
> The only way I've found to fix this is to add a manual #define for this
> symbol to autoconf.h
>
> The config option IS in i386/defconfig, but for some reason doesn't get
> put into .config
>
> if I add it to .config manually, it gets removed when I run make (?!?).
>
> I don't think this happens if I delete .config and make one from scratch.
It seems when you did "make oldconfig" you said "no" to all cpu options.
You should select the cpu type(s) you want to run your kernel on.
Run "make menuconfig" and select the appropriate cpu types in
Processor type and features
Processor support
cu
Adrian
--
"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-02-07 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 21:29 2.6.2-mm1 won't compile (been doing this since 2.6.1-mm2 or so) Robert F Merrill
2004-02-07 21:36 ` Adrian Bunk [this message]
2004-02-07 22:05 ` Robert F Merrill
2004-02-08 1:02 ` Adrian Bunk
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=20040207213646.GE7388@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=griever@t2n.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