shym

In that paragraph, I mean that you need two versions of the runtime: the one to run on host (that will be linked in `ocamlopt.opt`) and one to run on...

> the cross-compilers built in this way still only work when the host and target have the same word size, is that right? Indeed, it doesn’t try to address this...

> Nothing looks wrong in that PR, but the devil lies in the details, so a lot of testing is needed, to confirm native builds are not affected and that...

> Another naïve question: is it right that these steps would be avoided/combined with the build of the cross-compiler if we are able to build the compiler "out-of-tree"? Certainly, the...

I've updated this PR with: - a fix to ensure that `LD` and `PACKLD` are set to `false` when building a cross compiler _and_ that the target-prefixed `ld` cannot be...

> > To build a cross compiler you first need to have a non-cross compiler of the same version installed in your $PATH. > > I believe (but have not...

I just updated the PR with: - a last step in the `crossopt` recipe to (re)build the compiler libs for the target (they have been built for the host as...

> It is probably set somewhere in the CI, but I can't find where exactly. `qemu-aarch64` is explicitly called in CI with the corresponding path: https://github.com/shym/ocaml/blob/f47058c29fdddf187d6ae6df2ef58a37dd688b0d/.github/workflows/build-cross.yml#L208 > Maybe this should...

Rebased on `trunk` to handle the superficial conflicts.

Thank you for this thorough review @shindere! (I rebased to handle the conflicts before I start addressing all your comments, to make future rewrites easier to proofread.)