Jarkko Hietaniemi wrote:
> The bootstrapping may take several rounds as Parrot learns
...
> - execute (collect output) (note that execution may not be native)
I don't think these two (cross-compile and build-own-tools) are
strictly compatible goals.
If you are going to build your own tools and use them, those
tools will need to run in the local environment.
At some point a cross-compiler will be trusting its cross-compilation
tool to run in the other environment.
Answering "what is a tool I will need to complete the process" and
"what tools are part of the deliverable" could give a compilation
procedure in which the intersection of the answers gets built twice.
Testing non-native executables is tricky too. A protocol for
how to do it, with either remote execution or emulation being
easy to configure, would help. Emulators that pretend to be a
remote hosts can make the second a special case of the first, but
wrapping scripts can make a remote machine seem like a special case
of an emulator just as easily.
--
David Nicol 816.235.1187
.sig file closed by executive order
