Am Mittwoch, 3. November 2010, 21:36:50 schrieb Andrew: > 03.11.2010 22:08, KP Kirchdoerfer пишет: > > Am Mittwoch, 3. November 2010, 20:41:23 schrieb Andrew: > >> 03.11.2010 20:53, KP Kirchdoerfer пишет: > >>> Am Mittwoch, 3. November 2010, 18:12:59 schrieb Andrew: > >>>> 03.11.2010 18:26, KP Kirchdoerfer пишет: > >>>>> Hi Andrew; > >>>>> > >>>>> the target buildtool.pl buildclean kernel is broken after support for > >>>>> multiple archs. > >>>>> (Sorry, catched a cold and I'm too dumb to fix it myself, still > >>>>> trying to understand how to compile another arch :)) > >>>>> > >>>>> kp > >>>> > >>>> Now it should work. > >>> > >>> Thx, it works. > >>> > >>> What about the file > >>> Bering-2.6.35.8.config-i686.patch > >>> > >>> in source/linux? It looks it won't be needed and is useless looking at > >>> it' s content? > >>> > >>> kp > >> > >> It's placed for unification for other archs - to provide one config, and > >> patches for config to get specific platform config. For i686 it does > >> nothing except scripts unification (I can't place blank file because > >> buildtool treats it as download failure). > > > > Ok; > > > > Is it possible to start with a generic setup ( 486 with X86 > > optimizations, no 2TB file, no SMP support etc) as platform where the > > different arch could be added? > > > > I think about this as base (and default) on which others can build > > upon... > > It's no difference which file is 'base', and which will be made from it > via patching. Even base file can be sonething > > > Maybe then it's easier to understand how to _add_ extra archs? > > It's enough easy :) Make your own config file; then - diff it to 'base' > config to obtain patch (linux-xxxxx.conf-$(ARCH).patch); add this patch > into CVS and add link on it into linux buildtool.cfg; modify > buildlool.cfg for moddb and initrd - you need to copy $(package)-i686 > section to $(package)-$(ARCH) and replace everywhere in included > filenames i686 link to $(ARCH). And, in the end, add new arch name into > Masterinclude.mk. That's all :) > It'll be good if somebody added support for new package type - > 'multipackage' - that will be a template for any arch... Or I'll try to > add hack - include file generator for multiple archs into makefile :) > > > I prefer to go the way from a general setup to optimized ones instead > > vice versa. > > > > kp > > De-facto, nobody knows which kernel can be named 'optimized' - i486 > generic kernel also will have some 'tweaks', disabled features that are > meaningless for i486 (pci-express & pci-express cards, more than 1GB RAM > support, SMP, most SATA drivers and so on). And there is no difference, > which kernel will be considered as base (and will have dummy patch for > unification), and which - will be generated from base via patch.
Hi Andrew; I'd say the "unoptimized" 486 kernel should be the base, but that's nitpicking. ok, I start to get it :)) I've managed to build the necessary patch, removed kernel and linux (including .source by hand) and to rebuild the kernel with 486 process support for the start. I'm wondering why I just built one kernel, I thought "(for i in $(KARCHS); do \ " (from buildtool.mk in source/linux) loops over the archs to build every arch added in make/Masterinclude.mk. Either I'm still doing something wrong, or I'm misleaded. kp ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
