Richard Henderson <richard.hender...@linaro.org> writes: > On 04/19/2018 03:58 AM, Alex Bennée wrote: >> I did start playing with crosstool-ng and Linaro's own ABE scripts but >> realised this could end up a massive time sync. What would be really >> helpful is if the respective maintainers could encode their EXACT >> STEPS for building their cross compilers into some docker recipes. > > Building a cross-compiler with an existing libc binary is easy. > Building a cross-compiler without a libc is harder, and involves > a bit of two-stepping to get things right. > > For someone who has never used docker, what's a recipe look like? > Just a shell script that gets run within a container? > Is there an opportunity to wget or local copy an existing libc > tarball/package to put us into the easy case?
Yes, it's just a bunch of steps run from a known starting state. Our debian-bootstrap.docker is probably the most complex as there is a seed step before you enter the container to run the setup steps. If you already have a built script for your compilers converting it to docker is fairly trivial. > >> Finally the end of the series has me adding Emilio's fp-test to the >> per-target builds. Unfortunately although some osdep.h and softfloat.c >> fiddling allows us to build in most cases I still can't build for >> example an i386 fp-test on an x86_64 host using the cross compiler as >> it triggers incompatibilities with config-host.h - in this case Int128 >> support. Currently I just hackily disable fp-test for non-64 bit >> platforms. > > It seems I can't even build fp-test for x86_64. > > CROSS-BUILD x86_64 guest-tests with cc > In file included from /home/rth/work/qemu/qemu/tests/fp/fp-test.c:14:0: > /home/rth/work/qemu/qemu/include/qemu/osdep.h:30:10: fatal error: > config-host.h: No such file or directory > #include "config-host.h" > ^~~~~~~~~~~~~~~ > compilation terminated. Weird as that works for me. Has configure been run? Are you in a external build dir? > > > r~ -- Alex Bennée
