On 18/03/15 18:18, Antti Kantee wrote:
Anyway, the vibe I'm guessing is that the description matches the tool wrappers already created by buildrump.sh. If at all possible, I think we should enhance buildrump.sh wrapper creation instead of having two sets of subtly different cross compilers. That would also unify the "kernel" and "userland" build, which is a direction I'd like to see us going into, i.e. fixing the dichotomies which were created when "userland" was invented ...
Ok, that's done (more than a few hours after I *hoped* I would be done with it).
Everything in rumprun now uses the wrappers created by buildrump.sh. There's also some amount of flag-passing going on, so if you run buildrump.sh with -F ACLFLAGS=-m32, your rumprun app-tools will automatically create -m32 binaries. That's intended to be useful especially when ARM supports hits prime-time. In other words, whatever ABI you select with compiler flags for buildrump.sh is supposed to automagically get used by app-tools.
As a side effect, we can now also do 32bit builds of /xen on x64, just run "./build-rr.sh xen -- -F ACLFLAGS=-m32". I added that to the travis build matrix.
The implementation a bit single-goal-oriented, but seems to work. We can of course adjust things as we learn more.
Now I think I can finally write the auto-test-script since I can just always compile with app-tools/cc without having to worry about passing the correct flags.
- antti
