.\" This troff source is processed to create all forms of the .\" 9FRONT DASH 1 book and the http://fqa.9front.org website. .\" NOTE: Purely experimental. Methods employed may change. .\" troff -ms -mpictures fqa5.ms | page .\" htmlroff -u -ms -mhtml fqa5.ms >fqa5.html .de FG \" .FG .ie h .html -

.el .BP \\$1.ps .br .. .po 1i \" page offset (from left) .fp 1 R LucidaSans .fp 2 I LucidaSansI .fp 3 B LucidaSansB .fp 4 BI LucidaSansI .fp 5 CW LucidaCW .paragraph 0 .margin 0 .HTML "FQA 5 - Building the System from Source .html - .html - FQA INDEX | .html - FQA 4 - 9front Installation Guide | .html - FQA 6 - Networking .html -

.SH .LG .ihtml h1

FQA 5 - Building the System from Source .ihtml h1 .NL .R .html - html | .html - pdf | .html - troff .FG thesource jpg .html - .ihtml h2
.SH 5.1 - Why should I build my system from source? .R .ihtml h2 Some reasons why you might actually wish or need to build from source: .ihtml ul
.IP • Updates have been committed since you performed the installation. • Test or develop new features. .LP .ihtml ul .html - .ihtml h2
.SH 5.2 - Building 9front from source .R .ihtml h2 .html - .ihtml h3
.SH 5.2.1 - Update sources .R .ihtml h3 9front uses .ihtml a git(1) .ihtml a to synchronize the system with the .ihtml a 9front repository: .ihtml a .P1 cd / bind -ac /dist/plan9front / git/pull -u gits://git.9front.org/plan9front/plan9front .P2 which is consolidated in the command: .P1 sysupdate .P2 After the tree is updated, recompile/build the updated programs as needed. .html - .ihtml h3
.SH 5.2.1.1 - hgrc .R .ihtml h3 .FG nosnackcar jpg .html - .ihtml h3
.SH 5.2.1.2 - git .R .ihtml h3 During installation, the 9front git repository is copied to .CW /dist/plan9front/.git , is .CW chmod 775, .R and is owned by user .CW glenda and group .CW sys . To update the repository when logged in as a user other than .CW glenda , add that user to group .CW sys . .html - .ihtml h3
.SH 5.2.2 - Building from source .R .ihtml h3 .B Note: A minimum of 512MB RAM is needed to link some programs. If less than 512MB is available, be sure to turn on swap before building (Read: .ihtml a .CW swap(8) ). .ihtml a .P1 # create any missing directories needed for the build cd / \&. /sys/lib/rootstub # build everything cd /sys/src mk install mk clean # build manpage indices cd /sys/man mk # build the papers and html (optional) cd /sys/doc mk mk html .P2 .B Note: Before cross compiling a kernel, the compiler, assembler, linker, and .ihtml a .CW paqfs(4) .ihtml a for the target architecture need to be built and installed (Read .ihtml a .I FQA 5.2.2.1 - Cross compiling). .ihtml a Build the kernel for 386: .P1 cd /sys/src/9/pc mk install .P2 Build the kernel for amd64: .P1 cd /sys/src/9/pc64 mk install .P2 Build the kernel for arm / Raspberry Pi: .P1 cd /sys/src/9/bcm mk 'CONF=pi' install mk 'CONF=pi2' install .P2 Build the kernel for arm64 / Raspberry Pi 3: .P1 cd /sys/src/9/bcm64 mk install .P2 Read: .ihtml a .I FQA 7.2.5 - How do I install a new kernel? .R .ihtml a .html - .ihtml h4
.SH 5.2.2.1 - Cross compiling .R .ihtml h4 To cross compile, simply set the .CW objtype environment variable prior to running the build. For example, to build all the amd64 binaries on a 386 system: .P1 # create any missing directories needed for the build cd / \&. /sys/lib/rootstub cd /sys/src objtype=amd64 mk install .P2 .html - .ihtml h2
.SH 5.3 - Building an ISO .R .ihtml h2 The 9front ISO is a livecd that also serves as install media. .B Note: Currently, only the 386 and amd64 architectures have downloadable ISOs (rpi has a bootable image). Read: .ihtml a .I FQA 8.9 - Bootstrapping architectures not included on the ISO .R .ihtml a for more information on booting other architectures. .P1 # put your root file system into /n/src9 bind /root /n/src9 # put your hg repository there bind -ac /dist/plan9front /n/src9 # build the iso cd /sys/lib/dist mk /tmp/9front.$objtype.iso .P2 .html - .ihtml h2
.SH 5.4 - Common Problems when Compiling and Building .R .ihtml h2 Most of the time problems in the build process are caused by not following the above directions carefully. People who complained about this section of the FQA have so far not submitted anything better. Good luck. ./" 5.4 should mention that sometimes you end up with a .8 file in a bad ./" state which can usually be resolved by deleting the .8 file or mk clean .html - .ihtml h2
.SH 5.4.1 - Updating compilers .R .ihtml h2 Changes to the compilers may necessitate updating the compiler before rebuilding the rest of the system: .P1 cd /sys/src/cmd/cc; mk install # choose the appropriate compiler for your architecture cd /sys/src/cmd/6c; mk install .P2 .html - .ihtml h2
.SH 5.4.2 - Trouble updating the compilers .R .ihtml h2 From the 9front mailing list: .P1 If you didn't 'mk nuke' your libc you can build the assembler and linker first: for(i in (6a 6l))@{ cd /sys/src/cmd/^$i && mk install } Then you may rebuild the rest of the system. If you did 'mk nuke': * if you use cwfs, copy older libc from dump and then do the above 9fs dump cp /n/dump/2024/... * if you use hjfs, copy updated binaries from the iso box. 9fs iso && cp /n/iso/amd64/bin/^(6a 6c 6l) /amd64/bin/ It would be nice to have a way of these updates notifying people of such manual steps. But for the time being I would suggest perusing the mailing lists when doing large updates. Thanks, moody .P2 Read: .ihtml a .I Re: [9front] Error compiling libc/amd64/main9.s and/or main9p.s .R .ihtml a .html -
.html - FQA INDEX | .html - FQA 4 - 9front Installation Guide | .html - FQA 6 - Networking