Re: [Ltib] Avoiding ltib preconfiguring a local kernel

[Stuart Hughes]

Hi Colin,

Currently LTIB always copies something to .config.  It does this IIRC as
we need to run 'make oldconfig' on something to align possibly old
configs with newer kernels.

The best you can do at the moment is to name one of the default configs
that are under arch/$LINTARCH/configs/ .  If this named file is no in
your config/platform/imx21ads/, LTIB will search for this in your kernel
source tree and then copy it to the .config.  This means you'd need to
keep your named defconfig under source control rather than the .config.

This is probably a better option too if you can tolerate it as
the .config is modified when you run mconf/conf on it.

Regards, Stuart

On Tue, 2008-12-16 at 09:41 +0000, Colin Helliwell wrote:
> I am trying to build the kernel from a local directory. I can't see how to
> stop ltib copying its 'built in' kernel config for the platform over to
> .config :   "cp -f
> /home/ltib/config/platform/imx21ads/linux-arm-2.4.20-celf3-imx21ads.config.d
> ev ./.config"
> 
> Ltib is from last week's cvs head.
> 
>  
> 
> The FAQ suggests the ltib config menu should have an option for the default
> kernel config it is going to apply ("kernel preconfig"), but I can't spot
> this when I run it.
> 
> Because my kernel will be under source control independent of ltib, I want
> to be able to have the kernel built always according to the .config in the
> kernel source tree, not any other.
> 
> Thanks.
> 
>  
> 
> 
> 
> 
> _______________________________________________
> LTIB home page: http://bitshrine.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib