On Fri, May 18, 2007 at 04:19:20PM -0700, Randy Dunlap wrote: > On Fri, 18 May 2007 14:46:02 -0700 Linda Walsh wrote: > > > Randy Dunlap wrote: > > > On Fri, 18 May 2007 12:32:47 -0700 Linda Walsh wrote: > > > > > > > > >> Seems there is an include of s390 based config in file > > >> drivers/crypto/Kconfig: source "arch/s390/crypto/Kconfig" > > >> > > >> The line doesn't seem to be need for an i386 build (haven't > > >> tried x86_64 though). > > >> > > >> I take it that this was a braino? > > >> > > > > > > Does it cause a problem? If yes, what problem? > > > > > ---- > > Yes. My source tree has unrelated architectures removed, > > as a result when building i386 or x86_64, the config tools try to > > include files from the s390 architecture. It isn't there. > > I'm building x86, why should I be including files from other > > architectures. It is hierarchically unclean. > > Yes, it is. What removes all arch-except-i386-and-x86_64 from your > kernel tree? Can't it also do > $ sed @source "arch/s390/crypto/Kconfig"@#source "arch/s390/crypto/Kconfig"@ > at the same time? > > Who supports a pared-down kernel tree like this?
On op of this I have previously discussed with Roman Zippel the possibility to have _one_ include hirachy for Kconfig files. So that kconfig would fetch all Kconfig files for all archs. Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/