From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [kvm-ppc-devel] Top level kvm-userspace directory getting crowded ... need new dir for qemu dependencies Date: Sun, 02 Mar 2008 18:41:32 +0200 Message-ID: <47CAD8BC.5000608@qumranet.com> References: <1203922225.9895.6.camel@thinkpad.austin.ibm.com> <47C283BA.8000106@qumranet.com> <1204046679.6589.8.camel@thinkpad.austin.ibm.com> <1204129772.2532.31.camel@basalt> <47C59111.1080102@qumranet.com> <4D4A90C0-9771-4A83-9E22-CA9D3177F30D@suse.de> <1204138586.2532.56.camel@basalt> <47C5B941.2020509@qumranet.com> <1204142247.2532.70.camel@basalt> <47C66DDA.7000808@qumranet.com> <1204230532.12181.40.camel@thinkpad.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel , kvm-ppc-devel , Hollis Blanchard To: jyoung5@us.ibm.com Return-path: In-Reply-To: <1204230532.12181.40.camel@thinkpad.austin.ibm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Jerone Young wrote: > So I forgot to CC all the interested parties on this list (sorry about > that I wasn't thinking at the time), but I did start up a conversation > on linuxppc-dev on the subject of splitting out libfdt from dtc. Mainly > to get the thought of what the dtc folks thought about splitting out > libfdt. > > The outcome of this discussion is the point of libfdt is to be > integrated into different projects. I could not make a good argument at > all as to why it should be split out (actually I did a terrible job at > it :-)). A good analogy was made also as this is "equivalent to > splitting libcrypto out of openssl". > > So the concessious from others in the libfdt community is the it should > go in the project. This would be in line with what Hollis has been > saying on the list. > > Now for us we can do one of the following options: > 1) Integrate libfdt into our kvm-userspace > or qemu (which would then require going upstream qemu folks also agree). > > 2) Can use wget or something to first grab the dtc source and get libfdt > from it. Then place in our make file and build it. As well as point > cflags & ldflags to it. (This can be done, though I wanted to avoid > going this route) > > We definitely won't make the build so complicated as to depend on wget and Internet connectivity, so we'll just plant the tree in kvm-userspace.git. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/