[lowrisc-dev] building lowRISC binaries with current
Dr Jonathan Kimmitt
jrrk2 at cam.ac.uk
Wed Oct 24 07:02:53 BST 2018
Many thanks for that investigation, I think the procedure we already have using debootstrap is more robust at the present time, even if certain libraries must be added outside of the tool. There is another tool called multistrap that does a similar job but is also rather O/S specific. However since mmdebstrap is rather new I’ve no doubt these issues will be cleared up soon.
Sent from my iPhone
> On 24 Oct 2018, at 02:58, Luke Kenneth Casson Leighton <lkcl at lkcl.net> wrote:
> i can confirm that both mmdebstrap and the process listed by john,
> above, work... with one small caveat for mmdebstrap: i had to ctrl-z
> background it within a few seconds (you have about a minute), and
> manually copied over the qemu-riscv64-static binary into the chroot's
> usr/bin directory.
> that program was *DELETED* at the end of the mmdebstrap, so had to be re-added.
> also... long story (as you'll be able to see from the thread), if you
> happen to be using a recent host-based linux kernel less than 4.15
> (i'm using 4.13 and really *really* cannot do any "rebooting", or
> trust anything that's had "spectre" mitigation added to it to not
> screw up my USD $2500 early-skylake-based laptop), you *will* need to
> run the update-binfmts parts of the advice listed in the page below,
> ANY and EVERY time that the /usr/bin/qemu-riscv64-static program is
> so, just to be clear: you need to make that copy (from git latest) of
> qemu-riscv64 into *BOTH* /usr/bin/qemu-risc64-static *AND* into the
> chroot *AND THEN* run that update-binfmts command.
> according to the info reported by kilobyte and others, if you're on a
> very recent host linux kernel things should work just fine.
More information about the lowrisc-dev