Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Bur <cyrilbur@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] linux: Build and install kernel selftests
Date: Wed, 16 Mar 2016 09:39:53 +1100	[thread overview]
Message-ID: <20160316093953.6fbfb09f@camb691> (raw)
In-Reply-To: <20160315222151.GM5053@free.fr>

On Tue, 15 Mar 2016 23:21:51 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Cyril, All,
> 
> On 2016-03-16 09:09 +1100, Cyril Bur spake thusly:
> > On Tue, 15 Mar 2016 10:24:13 +0100
> > "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:  
> > > On 2016-01-04 11:59 +1100, Cyril Bur spake thusly:  
> > > > This patch simply adds the ability to compile and install the kernel
> > > > selftests into the target at /usr/lib/kselftests.  
> [--SNIP--]
> > > > diff --git a/linux/linux-tool-selftests.mk b/linux/linux-tool-selftests.mk
> > > > new file mode 100644
> > > > index 0000000..b610599
> > > > --- /dev/null
> > > > +++ b/linux/linux-tool-selftests.mk
> > > > @@ -0,0 +1,42 @@
> > > > +################################################################################
> > > > +#
> > > > +# selftests
> > > > +#
> > > > +################################################################################
> > > > +
> > > > +LINUX_TOOLS += selftests
> > > > +
> > > > +ifeq ($(KERNEL_ARCH),x86_64)    
> > > 
> > > For i386, Buildroot sets KERNEL_ARCH=i386, so we may also want to handle
> > > that case, no?  
> > 
> > I think you're right but not super sure... I'll leave it up to an x86 boffin to
> > confirm that it's the correct thing to do :)  
> 
> Well, I guess you don't need a i386 guru to just add it, as that's what
> we already do for the kernel (see linux/linux.mk at 157).
> 
> [--SNIP--]
> > > > +SELFTESTS_DEPENDENCIES = bash    
> > > 
> > > It can also use libcap-ng, so you probably want to depend on it, too:
> > > 
> > >     /home/ymorin/dev/buildroot/O/host/usr/bin/i686-pc-linux-gnu-gcc -O2 -g
> > >       -std=gnu99 -Wall    validate_cap.c  -lcap-ng -lrt -ldl -o validate_cap
> > >     validate_cap.c:1:20: fatal error: cap-ng.h: No such file or directory
> > > 
> > > Ditto popt:
> > > 
> > >     /home/ymorin/dev/buildroot/O/host/opt/ext-toolchain/bin/../lib/gcc/
> > >     i686-pc-linux-gnu/4.7.2/../../../../i686-pc-linux-gnu/bin/ld: cannot
> > >     find -lpopt
> > >     collect2: error: ld returned 1 exit status  
> > 
> > I could add those dependencies I suppose, it would be nicer for everyone.  
> 
> Yes, please do.
> 
> > > However, as you said in the commit log, those are not fatal errors
> > > (although reported as such) and the build goes on successfully for the
> > > rest of the tests:
> > > 
> > > Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > > Tested-by: "Yann E. MORIN" <yann.morin.1998@free.fr>  
> > 
> > Are you happy for me to do a v3 based on your comments and leave both the
> > Reviewed-by and Tested-by tags?  
> 
> If all you do is:
>   - add the i386 case,
>   - add libcap-ng and popt dependencies,
> then yes, those tags of mine still stand.
> 

Ok, in doing it I had a thought, would it not just be best to add a "select"
line in the Config.tools.in line for libcap-ng and popt? That way people don't
HAVE to have it if they don't care about those tests.

I'm not sure as to the mapping between adding a select in a Config.in and using
"*_DEPENDENCIES =" in the .mk

> Don;t rename selftests into linux-selftests, though. It should be a
> separate patch that renames all the tools. For now, stay consistent with
> the existing tools, that is: do not prefix.

Yeah good point.

> 
> > Also, for what its worth, I've built and used it a lot for powerpc.  
> 
> Great! :-)
> 
> > Thanks again,  
> 
> My pleasure! :-)
> 
> Regards,
> Yann E. MORIN.
> 

      reply	other threads:[~2016-03-15 22:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04  0:59 [Buildroot] [PATCH v2] linux: Build and install kernel selftests Cyril Bur
2016-03-15  9:24 ` Yann E. MORIN
2016-03-15 22:09   ` Cyril Bur
2016-03-15 22:21     ` Yann E. MORIN
2016-03-15 22:39       ` Cyril Bur [this message]

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=20160316093953.6fbfb09f@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox