From: 邓尧 <torshie@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Release test framework
Date: Wed, 4 Dec 2013 14:22:58 +0800 [thread overview]
Message-ID: <CAOb3iuhg+Q=j3MJV+mjS0Nk_OxmanXhfSotHkRsjCuhk4Oa75w@mail.gmail.com> (raw)
In-Reply-To: <20131204060135.GZ24286@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
On Wed, Dec 4, 2013 at 2:01 PM, Rich Felker <dalias@aerifal.cx> wrote:
> On Wed, Dec 04, 2013 at 01:51:42PM +0800, 邓尧 wrote:
> > If busybox is used, the test framework itself would depend on musl-libc,
> > which means test test framework would depend on the test subject. In
> > theory, it's a bad bad idea.
> >
> > 0.02$
>
> The busybox used need not even be linked with musl; it could be a
> uclibc-linked binary from aboriginal, for example. The point was not
> to use busybox as any major part of the test framework, just to have a
> shell to run the script that would run all the tests from the
> libc-test package inside qemu.
>
Extracting test result isn't easy, and creating these initramfs and kernel
images are time consuming. qemu-user may be a better choice, I'm not sure
about the stability of qemu-user though. The following shows qemu-user
could easily run a simple userspace program of a different architecture:
hoolala@ubuntu:/tmp$ cat hello.c
#include <stdio.h>
int main() {
printf("hello\n");
return 1;
}
hoolala@ubuntu:/tmp$ arm-linux-gnueabi-gcc hello.c -static
hoolala@ubuntu:/tmp$ qemu-arm ./a.out
hello
hoolala@ubuntu:/tmp$ echo $?
1
[-- Attachment #2: Type: text/html, Size: 1687 bytes --]
next prev parent reply other threads:[~2013-12-04 6:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 22:11 Rich Felker
2013-12-04 5:51 ` 邓尧
2013-12-04 6:01 ` Rich Felker
2013-12-04 6:22 ` 邓尧 [this message]
2013-12-04 7:06 ` Rich Felker
2013-12-04 7:16 ` Szabolcs Nagy
2013-12-04 7:48 ` Szabolcs Nagy
2013-12-09 10:56 ` 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='CAOb3iuhg+Q=j3MJV+mjS0Nk_OxmanXhfSotHkRsjCuhk4Oa75w@mail.gmail.com' \
--to=torshie@gmail.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).