Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot's support of ltp-testsuite
Date: Mon, 24 Jan 2011 15:31:51 +0100	[thread overview]
Message-ID: <20110124153151.172e43a1@surf> (raw)
In-Reply-To: <AANLkTik1WhgfrQtEjh6_TH2zn5sQMbs_7ixFPPOpghVR@mail.gmail.com>

Hello David,

Please keep the Buildroot list in Cc for all Buildroot-related topics.

On Thu, 20 Jan 2011 20:27:47 -0800
David Fisher <dfisher769@gmail.com> wrote:

> Thank you very much for answer.
> I am trying to evaluate the possibility of using the LTP test suite for
> embedded software, basing on Linux kernel, which was built with the Build
> Root tool, using uClibc.
> 
> I found in your posting at Free Electronics "On the road to Buildroot
> 2009.08", from August 3, 2009, that ltp-testsuite is on the list of upgraded
> packages.  Also there is ltp-testsuite directory (under buildroot/package),
> so it was my understanding that it could be compiled under uClibc, exactly
> as it could be compiled under non embedded Fedora, which uses glibc.
> (By the way the version of August 30, 2009, -- 20090830, which is used there
> would not compile even under Fedora, because of bug.  The "tst_exit"
> function, used in the "inh_capped.c" with an argument, while the prototype
> of this function, defined in the "test.h" defines it as
> "void tst_exit(void) LTP_ATTRIBUTE_NORETURN*;*", however in the newer
> versions of the ltp this bug is fixed.  I modified the version's date in all
> the related files of the ltp-testsuite and tried to compile, however without
> success.  The file "ballistaRPC.h, which is generated automatically using
> rpcgen, and therefore should not be edited, has a line *#include <rpc/rpc.h>
> *, while the rpc.h file does not exist.)
> 
> *My major two questions are:*
> *1. Is there any possibility to build (at least a portion of) LTP test suite
> above uClibc and test with it the kernel?  If yes, how to do it?*

It is probably possible, but not with the default uClibc configuration
used in Buildroot. The LTP test-suite uses some functions that are
considered legacy: those functions are present in glibc, but not in
traditional configurations of uClibc. With enough effort, you can
probably find all the uClibc options needed to generate an uClibc that
has all the required features to run ltp-testsuite. I have however
never tried this, so I can't say for sure if it's feasible or not.

> *2. If not, could you please provide with more details how to use the ltp,
> built on external toolchain that relies on glibc, which you mention in your
> email to me?*

If you're using Buildroot 2010.11 (the latest stable version at this
time), then you have to first download and install a glibc toolchain
separatly. If you're working on ARM, my recommandation would be the
CodeSourcery toolchains. If you're working on another architecture, you
may want to try Crosstool-NG to generate a toolchain. Once you have the
toolchain, just configure Buildroot to use it as an external toolchain.

If you're using Buildroot Git (which will become the next stable
version, at the end of February), then Buildroot can automatically
download and install an external toolchain for you, at least for the
CodeSourcery toolchains on ARM, MIPS, PowerPC and SH.

Note that the ltp-testsuite package has been upgraded recently in
Buildroot:
http://git.buildroot.net/buildroot/commit/?id=a72a670489547a3ca645ff7c3a0d9c3fb66eab51.
The version used is newer than the one you would use if you work with
Buildroot 2010.11.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2011-01-24 14:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14  2:34 [Buildroot] buildroot's support of ltp-testsuite David Fisher
2011-01-14  7:53 ` Thomas Petazzoni
     [not found]   ` <AANLkTik1WhgfrQtEjh6_TH2zn5sQMbs_7ixFPPOpghVR@mail.gmail.com>
2011-01-24 14:31     ` Thomas Petazzoni [this message]
2011-01-26  4:02       ` David Fisher
2011-01-29  9:11         ` Thomas Petazzoni
2011-01-29 10:58           ` Will Newton
  -- strict thread matches above, loose matches on Subject: below --
2011-01-14  3:26 David Fisher

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=20110124153151.172e43a1@surf \
    --to=thomas.petazzoni@free-electrons.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