From: Guenter Roeck <linux@roeck-us.net>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Tony Breeds <tony@bakeyournoodle.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Fwd: Rough notes from testing unconference
Date: Mon, 25 Aug 2014 03:43:24 -0700 [thread overview]
Message-ID: <53FB134C.90203@roeck-us.net> (raw)
In-Reply-To: <CACxGe6t=Sj+OLVOyCYCa+r5kS4paxmXapTA0Xe43TX1rHtFJYA@mail.gmail.com>
On 08/25/2014 02:23 AM, Grant Likely wrote:
> On 24 Aug 2014 19:14, "Guenter Roeck" <linux@roeck-us.net> wrote:
>>
>> On 08/24/2014 10:12 AM, Grant Likely wrote:
>>> ktest depends on a rootfs from elsewhere. I'm only mildly familiar
>>> with aiaiai, but it appears to be the same situation. The gap I see is
>>> the ability to cross compile the kselftest test cases and the ability
>>> to create a rootfs including the test cases for any architecture. A
>>> tool to solve that problem should be usable by both ktest and aiaiai.
>>>
>> Exactly.
>>
>> Wonder if it would be possible to publish prebuilt toolchains on kernel.org
>> which are suitable to create the root file system.
>
> I want to experiment with crosstool-ng, and yes I think the binaries
> should go on kernel.org. The current toolchains on kernel.org are
> built by Tony Breeds using Segher Boessenkool's buildall scripts (gcc
> only, no glibc). There are patches to buildall which will build a
> libc, but I haven't had much success with them.
>
Building toolchains with the latest version of buildroot is working
pretty well for me.
Guenter
next prev parent reply other threads:[~2014-08-25 10:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140819163621.GA15109@linux.vnet.ibm.com>
2014-08-22 14:19 ` Grant Likely
2014-08-22 17:59 ` Shuah Khan
2014-08-22 18:08 ` Amit Kucheria
2014-08-28 21:54 ` Shuah Khan
2014-08-23 13:35 ` Bird, Tim
2014-08-23 21:12 ` Grant Likely
2014-08-30 1:09 ` [Ksummit-discuss] [kselftest] kselftest wiki (was RE: Fwd: Rough notes from testing unconference) Bird, Tim
2014-08-30 2:55 ` Shuah Khan
2014-08-30 5:15 ` Konstantin Ryabitsev
2014-08-23 8:12 ` [Ksummit-discuss] Fwd: Rough notes from testing unconference Fengguang Wu
2014-08-24 17:12 ` Grant Likely
2014-08-24 18:14 ` Guenter Roeck
2014-08-25 9:23 ` Grant Likely
2014-08-25 10:43 ` Guenter Roeck [this message]
2014-08-24 18:15 ` Geert Uytterhoeven
2014-08-24 18:37 ` Guenter Roeck
2014-08-24 18:47 ` Olof Johansson
2014-08-24 19:14 ` Jason Cooper
2014-08-24 19:16 ` Jason Cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53FB134C.90203@roeck-us.net \
--to=linux@roeck-us.net \
--cc=grant.likely@secretlab.ca \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=tony@bakeyournoodle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox