Hello Vimer! On 2/19/22 15:32, vimer wrote: > I apply patch[1] to sip source and pass for " machine `riscv64' not > recognized" error, but fail at last:
I suggest using qemu-based sbuild environment for building packages for riscv64. There is an outdated guide I wrote for sh4 [1] which explains on how to set up such an environment. Normally, you should be able to create such a changeroot with: # apt install sbuild # cd /srv # debbootstrap --no-check-gpg --include=debian-ports-archive-keyring --arch=riscv64 \ unstable sid-riscv64-sbuild http://ftp.ports.debian.org/debian-ports/ and use this configuration: glaubitz@nofan:~> cat /etc/schroot/chroot.d/sid-riscv64-sbuild [sid-riscv64-sbuild] description=Debian sid chroot for riscv64 type=directory directory=/srv/sid-riscv64-sbuild #groups=Debian,guest,d-i #profile=dsa #aliases=sid groups=root,sbuild,glaubitz,buildd root-groups=root,sbuild,glaubitz,buildd #command-prefix= #source-root-users=glaubitz,sbuild,buildd #run-setup-scripts=true #run-exec-scripts=true glaubitz@nofan:~> Then you can packages virtually natively using --arch=riscv64. Adrian > [1] https://wiki.debian.org/SH4/sbuildQEMU -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
