Date: Tue, 18 Jan 2005 21:15:19 +0100 (CET)
From: Roman Zippel <zippel@linux-m68k.org>
To: Andreas Gruenbacher <agruen@suse.de>
cc: linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>,
       Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [kbuild 2/5] Dont use the running kernels config file by default
In-Reply-To: <20050118192608.423265000.suse.de>
Message-ID: <Pine.LNX.4.61.0501182106340.6118@scrub.home>
References: <20050118184123.729034000.suse.de> <20050118192608.423265000.suse.de>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 835
Lines: 21

Hi,

On Tue, 18 Jan 2005, Andreas Gruenbacher wrote:

> A user ran into the following problem: They grab a SuSE kernel-source
> package that is more recent than their running kernel. The tree under
> /usr/src/linux is unconfigured by default; there is no .config. User
> does a ``make menuconfig'', which gets its default values from
> /boot/config-$(uname -r). User tries to build the kernel, which doesn't
> work.

NAK. This isn't normally supposed to happen and it shouldn't be as bad 
anymore as it used to be. Removing these path doesn't magically create a 
working kernel.

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/