From: Cyril Bur <cyrilbur@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: Build and install kernel selftests
Date: Thu, 17 Dec 2015 12:25:20 +1100 [thread overview]
Message-ID: <20151217122520.6ffe6508@camb691> (raw)
In-Reply-To: <20151215173117.GA3596@free.fr>
On Tue, 15 Dec 2015 18:31:17 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
Hello Everyone,
> Baruch, Cyril, All,
>
> On 2015-12-15 08:37 +0200, Baruch Siach spake thusly:
> > On Mon, Dec 14, 2015 at 11:18:46PM +0100, Yann E. MORIN wrote:
> > > On 2015-11-25 10:53 +1100, Cyril Bur spake thusly:
> > > > +config BR2_LINUX_KERNEL_TOOL_SELFTESTS
> > > > + bool "selftests"
> > >
> > > Since the .mk has:
> > > SELFTESTS_DEPENDENCIES = bash
> > >
> > > then you must either depend on bash or select it here. I think a select
> > > is better, so:
> > >
> > > depends on BR2_USE_MMU # bash
> > > select BR2_PACKAGE_BASH
> >
> > But BR2_PACKAGE_BASH depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS.
>
> Gah... I missed that... Thanks for spotting! :-)
>
Ah I would totally have missed that too, thanks Yann and Baruch!
> > Should
> > BR2_LINUX_KERNEL_TOOL_SELFTESTS also depend on
> > BR2_PACKAGE_BUSYBOX_SHOW_OTHERS?
>
> Yes. With a comment stating so, like:
>
> config BR2_LINUX_KERNEL_TOOL_SELFTESTS
> bool "selftests"
> depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS # bash
> depends on BR2_USE_MMU # bash
> select BR2_PACKAGE_BASH
>
> comment "selftests needs BR2_PACKAGE_BUSYBOX_SHOW_OTHERS"
> depends on !BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
>
> (not so nice, but we already have it for openvmtools.)
>
Doesn't matter, I don't think we'll ever get the selftests looking 'nice'
anyway but that is an improvement.
On the note of dependencies - when I wrote the patch I was in two minds about
dependencies. Either this does the bare minimum to get the tests in and if the
user wants more tests to work/pass then they'll need to add things, or the
selftests depends on as much as possible to give as many tests passing as
possible. Based off this and discussion with a colleague, it might be better
that ticking the option to just select everything, if you're building the
selftests into your image it's because you want to be able to run them.
I haven't gone through and determined what the biggest set is but will do and
post v2.
> Regards,
> Yann E. MORIN.
>
next prev parent reply other threads:[~2015-12-17 1:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 23:53 [Buildroot] [PATCH] Add Linux kernel selftests building Cyril Bur
2015-11-24 23:53 ` [Buildroot] [PATCH] linux: Build and install kernel selftests Cyril Bur
2015-12-14 22:18 ` Yann E. MORIN
2015-12-15 6:37 ` Baruch Siach
2015-12-15 17:31 ` Yann E. MORIN
2015-12-17 1:25 ` Cyril Bur [this message]
2015-12-17 1:45 ` Cyril Bur
2015-12-17 18:07 ` Yann E. MORIN
2015-12-21 5:44 ` Cyril Bur
2015-12-21 9:25 ` Yann E. MORIN
2015-12-21 22:18 ` Cyril Bur
2015-12-21 22:25 ` Yann E. MORIN
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=20151217122520.6ffe6508@camb691 \
--to=cyrilbur@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.