Hi ----- Original Message ----- > Hi Pranith, > > Here is a proof-of-concept series for you to consider rolling into the TCG > tests > cleanup. It uses the existing docker make machinery to build a Debian > image which has arm, arm64 and ppc64el cross compilers in it. Now if > you run: > > make arm-tcg-tests > > It will do the requisite build of the docker image and then use that > to build the TCG tests in the appropriate build directory. > > These apply on top of your existing series. There is also a quick hack > to disable the running of the tests by default. I think we need two > stages, maybe a build-FOO-tcg-tests and run-FOO-tcg-tests. > > What do you think?
I like the idea, as long as you can also run the tcg tests without docker. How many of the qemu archs debian cross tools support? last time I looked there was annoying limitations, but I can't remember the details. crosstool-ng has perhaps more potential, especially if devs would share their config/samples (we could then have a cross-distro packaging with flatpack?) > Alex Bennée (4): > tests/docker: add basic user mapping support > new tests/docker/dockerfiles/debian-multiarch-cross.docker > tests/tcg: don't run tests by default > tests/tcg/Makefile: use docker target for arm-tcg-tests > > tests/docker/docker.py | 19 +++++++++++ > tests/docker/dockerfiles/debian-bootstrap.docker | 3 ++ > .../dockerfiles/debian-multiarch-cross.docker | 39 > ++++++++++++++++++++++ > tests/tcg/Makefile.include | 20 +++++++++-- > tests/tcg/arm/Makefile | 2 +- > tests/tcg/misc/Makefile | 4 +-- > 6 files changed, 81 insertions(+), 6 deletions(-) > create mode 100644 tests/docker/dockerfiles/debian-multiarch-cross.docker > > -- > 2.11.0 > >
