From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: eglibc testing?
Date: Thu, 16 Jun 2011 16:18:33 -0700 [thread overview]
Message-ID: <4DFA8F49.8000309@gmail.com> (raw)
In-Reply-To: <1308234598.25285.4740.camel@phil-desktop>
On 06/16/2011 07:29 AM, Phil Blundell wrote:
> On Thu, 2011-06-16 at 06:41 -0700, Khem Raj wrote:
>> I nfsmount eglibc builddir on target and run the testsuite. I see aroung
>> 10-15 fails. Havent run the testsuite in a while
>
> Maybe the right thing to do with eglibc would be to build a rootfs
> containing the testsuite, run it up in qemu-system-arm, and then
> engineer some IPC mechanism to get the test results back to the host.
using nfs isnt bad either since the tests excercise libraries from /lib
on target IOW installed eglibc.
> That way you would at least be testing something close to the real
> target kernel, rather than the qemu syscall emulation which I suspect is
> to blame for some of my failures.
>
> For gcc it'd probably be fine to just run the individual tests under
> qemu directly since they don't tend to have a lot of OS dependency.
>
Yes I think I should put together my mechanism somewhere and post it
and dejaGNU setup I use for cross testing
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-06-16 23:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 10:15 eglibc testing? Phil Blundell
2011-06-16 13:41 ` Khem Raj
2011-06-16 14:29 ` Phil Blundell
2011-06-16 23:18 ` Khem Raj [this message]
2011-06-17 10:13 ` Phil Blundell
2011-06-17 10:25 ` Richard Purdie
2011-06-17 10:41 ` Phil Blundell
2011-06-30 10:32 ` Phil Blundell
2011-06-30 14:29 ` Khem Raj
2011-08-04 9:24 ` Phil Blundell
2011-08-04 15:10 ` Khem Raj
2011-12-09 6:25 ` Khem Raj
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=4DFA8F49.8000309@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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.