Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] or1k system calls appear broken
Date: Sun, 10 Dec 2017 11:17:55 +0100	[thread overview]
Message-ID: <20171210101755.GH27558@waldemar-brodkorb.de> (raw)
In-Reply-To: <CAMo8BfLbTDTU+tZ2Qtp05borqYzwhpKgmLhMPgm_pqz-7T3ayQ@mail.gmail.com>

Hi Max,
Max Filippov wrote,

> On Thu, Dec 7, 2017 at 11:28 AM, Waldemar Brodkorb <wbx@openadk.org> wrote:
> > I checked the test suite and no syscall() is used.
> > Would it be possible for you to suggest a test case for syscall()?
> >
> > Then I can run the tests for all architectures, where I can do
> > runtime testing.
> 
> LTP ( http://linux-test-project.github.io )?

The problem with LTP is that some of the automatic tests via
qemu in system mode are done in a small environment, which not much
RAM or any hard disk. I somtimes try to make more architectures and
targets to work with LTP, but for this small cleanup I would
prefer a simple test case included in uClibc-ng-test.

Anyone?

best regards
 Waldemar

  reply	other threads:[~2017-12-10 10:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 13:09 [Buildroot] or1k system calls appear broken Joel Stanley
2017-11-21  3:56 ` Waldemar Brodkorb
     [not found]   ` <20171121092441.GW29237@lianli.shorne-pla.net>
2017-11-21 19:56     ` Waldemar Brodkorb
2017-11-28  6:49 ` Waldemar Brodkorb
2017-12-06  0:41   ` Stafford Horne
2017-12-06 12:38     ` Joel Stanley
2017-12-06 12:55       ` Stafford Horne
2017-12-06 18:20         ` Waldemar Brodkorb
2017-12-06 22:44           ` Stafford Horne
2017-12-07 19:28             ` Waldemar Brodkorb
2017-12-07 19:33               ` Max Filippov
2017-12-10 10:17                 ` Waldemar Brodkorb [this message]
2017-12-10 11:10                   ` Stafford Horne
2017-12-12 19:37                     ` Waldemar Brodkorb

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=20171210101755.GH27558@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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