From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot's support of ltp-testsuite
Date: Fri, 14 Jan 2011 08:53:20 +0100 [thread overview]
Message-ID: <20110114085320.29dfe769@surf> (raw)
In-Reply-To: <AANLkTin=kO3yG0t4MhDhBDP_Y4Y46Jt98Um7a7epVBy3@mail.gmail.com>
On Thu, 13 Jan 2011 18:34:48 -0800
David Fisher <dfisher769@gmail.com> wrote:
> The latest version of buildroot has a directory of
> .../buildroot/package/ltp-testsuite, which includes Config.in,
> ltp-testsuite.mk and five patch files.
> The third line of Config.in is "depends on BROKEN". As a result the
> ltp-testsuite could not be compiled under buildroot.
>
> Any plan to fix this problem, so the ltp-testsuite could be built?
This has been improved a bit in the current Git version, through the
following commit:
a72a670489547a3ca645ff7c3a0d9c3fb66eab51
However, beware that ltp-testsuite cannot be built with the default
Buildroot configuration for uClibc, as ltp-testsuite uses some legacy
functions that we don't enable in our default build of uClibc.
ltp-testsuite however builds fine with an external toolchain that
relies on glibc, and it even runs on ARM (some tests have issues, but
most of the tests were working correctly).
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-01-14 7:53 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 [this message]
[not found] ` <AANLkTik1WhgfrQtEjh6_TH2zn5sQMbs_7ixFPPOpghVR@mail.gmail.com>
2011-01-24 14:31 ` Thomas Petazzoni
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=20110114085320.29dfe769@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