From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753744AbbCaHrr (ORCPT ); Tue, 31 Mar 2015 03:47:47 -0400 Received: from shonan.sfc.wide.ad.jp ([203.178.142.130]:56518 "EHLO mail.sfc.wide.ad.jp" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753462AbbCaHro (ORCPT ); Tue, 31 Mar 2015 03:47:44 -0400 Date: Tue, 31 Mar 2015 16:47:40 +0900 Message-ID: From: Hajime Tazaki To: richard@nod.at Cc: linux-arch@vger.kernel.org, arnd@arndb.de, corbet@lwn.net, cl@linux.com, penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, netdev@vger.kernel.org, linux-mm@kvack.org, jdike@addtoit.com, rusty@rustcorp.com.au, mathieu.lacage@gmail.com Subject: Re: [RFC PATCH 00/11] an introduction of library operating system for Linux (LibOS) In-Reply-To: <5518F030.4040003@nod.at> References: <1427202642-1716-1-git-send-email-tazaki@sfc.wide.ad.jp> <551164ED.5000907@nod.at> <55117565.6080002@nod.at> <55118277.5070909@nod.at> <55133BAF.30301@nod.at> <5514560A.7040707@nod.at> <55152137.20405@nod.at> <5518F030.4040003@nod.at> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) X-Face: "+?b:_s\r$dbBx'Ur*k#`5|~\>v~i`PzaxANTx_S?J>:mTQrtm:c7'f5b~W2eX~Fl[0Pw,0bow)8r8Z5,D&>]C/'ujqr:fbY>]/52T^Q~cX*y5\?!"i<^Vp=zCNguAeyPH$`ZTv{di25X8,%@! MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org At Mon, 30 Mar 2015 08:41:52 +0200, Richard Weinberger wrote: > > one more concern on the out-of-arch-tree design is that how > > to handle our asm-generic-based header files > > (arch/lib/include/asm). we have been heavily used > > 'generic-y' in the Kbuild file to reuse header files. > > As noted before, libos is something in between. Maybe the asm-generic > stuff needs some modifications to make it work for libos. okay. > BTW: There is something really fishy wrt to your build process. > I did a ARCH=i386 build due to my regular kernel work and later a ARCH=lib build. > It seems to pickup old/unrelated object files. > After a make clean ARCH=i386 it build fine. > > ---cut--- > LIB liblinux-4.0.0-rc5.so > /usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linux/bin/ld: Warning: size of symbol `skb_copy_bits' changed from 10 in ./kernel/bpf/core.o to 441 in ./net/core/skbuff.o > ./net/ipv6/fib6_rules.o: In function `fib6_rule_lookup': > /home/rw/linux/net/ipv6/fib6_rules.c:34: multiple definition of `fib6_rule_lookup' (snip) right now arch/lib/Makefile isn't fully on the Kbuild system: build file dependency is not tracked at all. while I should learn more about Kbuild, I'd be happy if you would suggest how the Makefile should be. > ---cut--- > > While we're talking about the build process, how can I cross build libos? > Say a i386 libos on x86_64. For UML we have use SUBARCH. > i.e. make linux ARCH=um SUBARCH=i386 the cross build is not either implemented. if libos needs it, I'd start to think about the design: maybe SUBARCH-like mechanism is required. -- Hajime