[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

The brief status of Debian riscv porting --2022/11/06



Hi,

Over the past few months, the Deci team has been making continuous
optimizations to run autopkgtest on the riscv64 architecture. At the moment it seems that debci on riscv64 is in a good state[0]. It seems that britney's job queue finally can be reflected in the newest updated packages. Many thanks again to the Debci team for their hard work here. Of course, The PLCT lab[1] also provides a lot of help whether it is hardware resources or system maintenance.

The -latomic issue is one big problem for our porting now. @mafm thought of a workaround(modify dpkg-buildflags on riscv64 arch), but it also has certain unknowns. The best solution is to expect the patch that fixes the atomic problem to be merged by GCC upstream. But it looks like GCC people still have a lot of concerns[2] about the related patchset, Of course, the suboptimal solution is a patchset that can be backported from GCC upstream.

At last, if you have trouble finding RISC-V hardware resources and want to help port/debug Debian package on riscv64, please post here or ask on #debian-riscv IRC. Thanks again to plct labs for providing hardware resources to help with the Debian RISC-V port.


[0]: https://ci.debian.net/user/britney/jobs?package=&trigger=&suite%5B%5D=unstable&arch%5B%5D=riscv64&page=4&page=1.
[1]: https://github.com/plctlab/riscv-lab-access
[2]: https://patchwork.ozlabs.org/project/gcc/cover/20210505193651.2075405-1-cmuellner@gcc.gnu.org/

--
Regards,
--
  Bo YU

Attachment: signature.asc
Description: PGP signature


Reply to: