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

The brief status of Debian riscv porting --2022/10/22



Hi,

In the past two weeks, due to the atomic problem and the cargo build
dependency problem, the number of riscv64 built packages has been
maintained at about 15k[0], which is a little lower than before.
Because when is unknown the upstream of GCC will be able to merge the patch of solving the atomic issue, and the porter sends the
patch to build the affected package.

Another thanks to pabs, we maybe have some work to do about
cross-build for Debian riscv64. But limited by personal experience,
I cannot evaluate these specific jobs. Here, I just grep the pabs's
wiki[1] here.

```
Make the port available for maintainers and users to cross-build packages to:

    Add support to the binutils source package

    Add libc6*-dev-$arch-cross, libc6*-$arch-cross and linux-libc-dev-$arch-cross
packages to the cross-toolchain-base (for ftp-master.d.o arches) or
cross-toolchain-base-ports (for ports.d.o arches) source packages

    Add support to the current gcc-N source package

    Add metapackages to the gcc-defaults source package

    Add a crossbuild-essential-$arch metapackage to the build-essential
source package
```

I've tried building some of these packages and obviously need to add
riscv64 support (maybe with some help from the Debian toolchain folks for me).

[0]: https://buildd.debian.org/status/architecture.php?a=riscv64&suite=sid
[1]: https://wiki.debian.org/PortsDocs/New#Other_work

--
Regards,
--
  Bo YU

Attachment: signature.asc
Description: PGP signature


Reply to: