Re: Building a solid musl automated-testing framework

[Szabolcs Nagy <nsz@port70.net>]

* Bobby Bingham <koorogi@koorogi.info> [2014-08-04 00:10:12 -0500]:
> On Thu, Jul 31, 2014 at 05:47:16PM -0400, Rich Felker wrote:
> >
> > 1. Have a Makefile and a subdirectory full of cross compiler trees.
> >    The set of archs could be based purely on the set of cross
> >    compilers, computed by the Makefile based on directory contents.
> >
> > 2. Have the Makefile clone/pull one musl tree from upstream git and
> >    then clone/pull an additional copy of the tree per arch/subarch
> >    (with the set of archs determined as in point 1).
> >
> > 3. Build each musl (via recursive make, i.e. make calling configure
> >    and make in each musl clone) and install them into the cross
> >    compiler include/lib dirs for their corresponding cross compilers.
> >
> > 4. Do like points 2 and 3, but for libc-test repo.
> >
> > 5. Use the kernel, initrd, and qemu stuff from the adk-test-framework
> >    to build initrd images and run them.
> >
> 
> Last I looked, libc-test didn't support being built on one system and
> run on another.  Has this changed?
> 

libc-test builds and runs the tests using make

building works with a cross-compiler, but running them does not

so one can build on one system and then manually run the tests
on another, there is no automated method for this now