Bootstrapping Fedora on the new RISC-V architecture continues apace.
I have now written a small autobuilder which picks up new builds from the Fedora Koji build system and attempts to build them in the clean “stage4” environment.
Getting latest packages from Koji ... Running: 0 (max: 16) Waiting to start: 7 uboot-tools-2016.09.01-1.fc25.src.rpm | 11 MB 00:10 uboot-tools-2016.09.01-1.fc25 build starting tuned-2.7.1-2.fc25.src.rpm | 136 kB 00:00 tuned-2.7.1-2.fc25 build starting rubygem-jgrep-1.4.1-1.fc25.src.rpm | 24 kB 00:00 rubygem-jgrep-1.4.1-1.fc25 build starting qpid-dispatch-0.6.1-3.fc25.src.rpm | 1.3 MB 00:01 qpid-dispatch-0.6.1-3.fc25 build starting python-qpid-1.35.0-1.fc25.src.rpm | 235 kB 00:01 python-qpid-1.35.0-1.fc25 build starting java-1.8.0-openjdk-aarch32-18.104.22.168-4.160812.fc25.src.rpm | 53 MB 00:54 java-1.8.0-openjdk-aarch32-22.214.171.124-4.160812.fc25 build starting NetworkManager-strongswan-1.4.0-1.fc25.src.rpm | 290 kB 00:00 NetworkManager-strongswan-1.4.0-1.fc25 build starting MISSING DEPS: NetworkManager-strongswan-1.4.0-1.fc25 (see logs/NetworkManager-strongswan/1.4.0-1.fc25/root.log) ... etc ...
Given that we don’t have GCC in the stage4 environment yet, almost all of them currently fail due to missing dependencies, but we’re hoping to correct that soon. In the mean time a few packages that have no C dependencies can actually compile. This way we’ll gradually build up the number of packages for Fedora/RISC-V, and that process will accelerate rapidly once we’ve got GCC.
You can browse the built packages and build logs here: https://fedorapeople.org/groups/risc-v/