From: Maxim Grigoriev <maxim@tensilica.com>
To: buildroot@busybox.net
Subject: [Buildroot] ltp-testsuite package qustion
Date: Sat, 21 Mar 2009 10:45:30 -0700 [thread overview]
Message-ID: <49C527BA.9020404@tensilica.com> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE19090147DD12@mi8nycmail19.Mi8.com>
Thanks for your feedback.
>> In ./package/ltp-testsuite/ltp-testsuite.mk:
>>
>> - LTP_TESTSUITE_VERSION:=20070228
>> + LTP_TESTSUITE_VERSION:=20090228
That's what I did. Then, I found out that I have to redo the patches.
Does it mean nobody tried recent LTP tests ?
Thanks,
-- Maxim
H Hartley Sweeten wrote:
> On Friday, March 20, 2009 6:24 PM, Maxim Grigoriev wrote:
>
>> Hello everybody,
>>
>> Can somebody, please, tell me how I can change a version of
>> .../package/ltp-testsuite ?
>>
>> Is 20070228 a default ?
>> It seems to be hard-coded. And, ltp-testsuite patches do not apply
>> to a newer version.
>>
>> On the http://ltp.sourceforge.net/, the latest stable version is
>> claimed to be
>>
>> ltp-full-20090228.tgz
>>
>>
>
> In ./package/ltp-testsuite/ltp-testsuite.mk:
>
> - LTP_TESTSUITE_VERSION:=20070228
> + LTP_TESTSUITE_VERSION:=20090228
>
>
>> A Two-years old version does not work quite well with recent
>> versions of tools and kernel / kernel headers.
>>
>> One of the issues I observe is an undefined macro OPEN_MAX, which
>> was removed from limits.h. It's now a variable, which can be obtained,
>> say, by
>>
>> sysconf (_SC_OPEN_MAX).
>>
>> I'm hoping that switching to a newer version of LTP would fix this
>> problem.
>>
>> Any help on this will be highly appreciated.
>>
>
> Regards,
> Hartley
>
>
prev parent reply other threads:[~2009-03-21 17:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 1:24 [Buildroot] ltp-testsuite package qustion Maxim Grigoriev
2009-03-21 2:33 ` H Hartley Sweeten
2009-03-21 17:45 ` Maxim Grigoriev [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=49C527BA.9020404@tensilica.com \
--to=maxim@tensilica.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.