From Fedora Project Wiki
(本地编译测试)
(本地编译测试)
Line 34: Line 34:
 
= 本地编译测试 =
 
= 本地编译测试 =
  
下载 [https://fedorapeople.org/groups/risc-v/disk-images/ 第四阶段测试映像] 并参考以下介绍: [[Architectures/RISC-V/Disk Images]].
+
下载 [https://fedorapeople.org/groups/risc-v/disk-images/ 第四阶段测试映像] 并参考以下介绍: [[Architectures/RISC-V/Disk images]].
  
 
= 第四阶段的进展 =
 
= 第四阶段的进展 =
  
 
详见 [https://github.com/rwmjones/fedora-riscv-stage4 这个仓库].
 
详见 [https://github.com/rwmjones/fedora-riscv-stage4 这个仓库].

Revision as of 09:51, 2 December 2016

Shortcut:
Arch:RISC-V

这里记录所有关于 RISC-V 的 Fedora 软件包的信息 . 如果你想帮忙编译软件包或者修复有问题的软件包,你来对地方了。

自动编译工具

现在,所有软件包都用 自动编译工具 来编译。 which picks up packages as they are built in Fedora Koji build system and tries to rebuild them for RISC-V. The status of builds, build logs, RPMs and SRPMs can be found here.

The autobuilder can also be manually told to build a particular package, or to do a mass rebuild of every package in Fedora. If you need a particular package rebuilt, please ping rwmjones in the #fedora-riscv IRC channel on FreeNode.

We are currently only building Fedora 25 packages, but expect to move to Rawhide in the near future.

Fixing broken builds

Fedora has an upstream first policy and Fedora/RISC-V tries to stay as close as possible to this rule. Please send all your riscv64 changes to the upstream project. From there they will trickle down into Fedora.

If your package needs specfile changes, then you can ask the Fedora package maintainer to add those changes for you. However you should not do this for hacks, for patches which should go upstream, or for missing dependencies. If there are missing dependencies, work on the dependencies first. More information on this point.

If you have fixed a build, then there are two ways to get it into Fedora/RISC-V. Either do a primary arch build in Koji, which (if successful) the autobuilder will pick up automatically. Or ping rwmjones on #fedora-riscv and he will kick off a manual build.

策略上希望优先被提交主线

当前我们使用以下软件包的开发分支:

  • kernel
  • glibc
  • binutils
  • gcc
  • gdb

这是一个暂时的状态. 我们希望 RISC-V 尽快提交他们的修改到相应的项目主线。

本地编译测试

下载 第四阶段测试映像 并参考以下介绍: Architectures/RISC-V/Disk images.

第四阶段的进展

详见 这个仓库.