1. 74
  1.  

  2. 9

    One of my core goals with sr.ht is to encourage portable software to proliferate!

    Thank you!

    1. 8

      Glad you like this. This is also why I offer FreeBSD builds and I’m working on *BSD, Minix, etc.

    2. 3

      This is great! What kind of patches to distros are required for a port to RISC-V?

      I know strace is highly non portable because it has to know about syscall formats. What other packages have non portable code? I imagine video players and the like probably do due to optimizations, but a lot of code should be pure C. Musl was mentioned and I’d be interested in hearing details.

      1. 5

        strace isn’t bad, it just uses linux-headers to do its job. Others like libffi require more work. If you’re curious about musl, check out the main RISC-V patch:

        https://github.com/riscv/riscv-musl/commit/6a4f4a9c774608add4b02f95322518bd2f5f51ee

        As well as the patches I wrote as part of the Alpine Linux porting effort:

        https://github.com/riscv/riscv-musl/pulls/ddevault

        If you have any specific questions feel free to ask.

      2. 3

        This is cool, I am glad there are more people using RISC-V.

        I do wish it were easier to figure out what is needed to run on an FPGA. I guess for the moment emulation with QEMU is the easy way to practically run RISC-V.

        1. 6

          QEMU or that Unleashed board (which is as expensive as the (much faster) Talos Blackbird POWER9 system).

          The 64-bit, unix-capable cores probably don’t even fit on an FPGA, and if they do, it’d be painfully slow.

        2. 2

          This is so cool; thank you to the OP.