Line 90: | Line 90: | ||
rpmbuild --with bootstrap ... | rpmbuild --with bootstrap ... | ||
It fails (consistently) at: | |||
Adding szl_PL | |||
Adding ta_IN | |||
Adding ta_LK | |||
Adding tcy_IN.utf8 | |||
cannot lock new archive: Permission denied | |||
=== GCC (RWMJ) === | === GCC (RWMJ) === |
Revision as of 08:55, 17 August 2016
RISC-V (pronounced "RISC Five") is an open source instruction set architecture (ISA). This project, informally called Fedora/RISC-V, aims to get Fedora bootstrapped on the RISC-V (64 bit) architecture.
Downloads
- http://copr-fe.cloud.fedoraproject.org/coprs/rjones/riscv/
- COPR repository (for Fedora 24/x86_64) containing: QEMU, Spike, cross-compiler toolchain
- https://github.com/rwmjones/fedora-riscv
- Git repository containing the bootstrapping work. Read the README file!
- http://oirase.annexia.org/riscv/
- Interim stage3 disk image.
Status
Last updated: 2016-08-16
Status: The stage3 disk image boots to a shell, with GCC, numerous developer utilities, and rpmbuild.
I have started using the stage3 to build stage4 RPMs.
For the latest information, see: https://github.com/rwmjones/fedora-riscv
Communications
There is no specific mailing list. Use Fedora devel for now.
On FreeNode IRC: #fedora-riscv
People
(add your name here)
Building packages in stage3
The stage3 environment can be built from source or you can download a snapshot binary image. See above for links to git etc.
Pick a package which:
- has very few dependencies
- is written in C or C++
- is part of Fedora @Core
Grab the source RPM from Koji.
Copy the source RPM into the stage3 disk image. The disk image must not be running when you do this:
virt-copy-in -a stage3-disk.img the_package.src.rpm /var/tmp/
Boot the disk image in qemu:
make boot-stage3-in-qemu
Inside the VM you can now "install" the source RPM, which makes it available under /rpmbuild
:
rpm -i /var/tmp/the_package.src.rpm cd /rpmbuild/SPECS
You may need to disable hardened build by adding:
%undefine _hardened_build
to the spec file. Use vim
to edit files.
You can now try building the package:
rpmbuild -ba the_package.spec --define "debug_package %{nil}"
If it builds successfully, brilliant! More usually this will require many cycles of debugging and fixing things. Removing dependencies or parts of the spec file is an option for these stage3 builds.
If you get a build, it will be in /rpmbuild
inside the VM. sync and shut down the VM, then do:
virt-copy-out -a stage3-disk.img /rpmbuild ./
and the files will be downloaded to ./SRPMS and ./RPMS in the current directory. Note: Keep the source RPM too, especially if you modified it.
Add notes to the section below. Also come to #fedora-riscv
and discuss where to put your built packages.
Notes on packages built so far
zlib (RWMJ)
Done
filesystem (RWMJ)
Done
glibc (RWMJ)
rpmbuild --with bootstrap ...
It fails (consistently) at:
Adding szl_PL Adding ta_IN Adding ta_LK Adding tcy_IN.utf8 cannot lock new archive: Permission denied
GCC (RWMJ)
GCC can now be built from source inside the chroot. Next step is to build from the Fedora GCC SRPM.
gawk (RWMJ)
Done.
Hits "all-recursive" bug in make (or GCC?)
Making all in . Makefile:742: recipe for target 'all-recursive' failed
Added this to the spec file as a workaround:
sed 's/\$(am__cd) \$\$subdir \&\&/cd $$subdir ;/g' -i Makefile.in