From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 5119A92B for ; Sun, 24 Aug 2014 18:47:49 +0000 (UTC) Received: from mail-vc0-f179.google.com (mail-vc0-f179.google.com [209.85.220.179]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 27AD92022E for ; Sun, 24 Aug 2014 18:47:48 +0000 (UTC) Received: by mail-vc0-f179.google.com with SMTP id hq11so14034468vcb.24 for ; Sun, 24 Aug 2014 11:47:47 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <53FA30CC.9020404@roeck-us.net> References: <20140819163621.GA15109@linux.vnet.ibm.com> <20140823081245.GA16949@localhost> <53FA30CC.9020404@roeck-us.net> Date: Sun, 24 Aug 2014 11:47:47 -0700 Message-ID: From: Olof Johansson To: Guenter Roeck Content-Type: text/plain; charset=UTF-8 Cc: Segher Boessenkool , "ksummit-discuss@lists.linuxfoundation.org" Subject: Re: [Ksummit-discuss] Fwd: Rough notes from testing unconference List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, Aug 24, 2014 at 11:37 AM, Guenter Roeck wrote: > On 08/24/2014 11:15 AM, Geert Uytterhoeven wrote: >> >> On Sun, Aug 24, 2014 at 7:12 PM, Grant Likely >> wrote: >>> >>> Cross building the kernel isn't the problem. That's easy. Getting a >>> rootfs and the tests into the rootfs can be hard, depending on the >>> platform (a problem for some embedded targets). >> >> >> In the past, I have used OpenWRT to build the rootfs for the test >> target. >> > I very much prefer Grant's direct method - it ensures that the available > test code is automatically integrated into the root file system, and that > there are no architecture / target dependencies. > > For my part I have used various means to create root file systems for my > own tests, depending on the architecture. I see it as significant > improvement > to have it all together in a single place, in our control, and to have it > as simple as possible. Yep. Unfortunately, having a cross-toolchain that includes libc is a significant complexity improvement over just having one that can build a kernel. I wouldn't mind having pre-built rootfs:es available just like we have toolchains today, but that won't help me when it comes to building the kselftest binaries. I have traditionally been using Segher's buildall (http://git.infradead.org/users/segher/buildall.git) to build and populate toolchains locally, and that will no longer be enough. Unless someone convinces Segher to improve his scripts, of course. :) -Olof