.\" this is an extract of port.ms: change that too if needed.pl 9999.SHInstalling hosted Inferno from source.SHOverview.PPLike the native kernels.CW emurelies on several auxiliary libraries (the source of whichit often shares with the native kernels).Emu itself is built by the.CW mkfilein the.CW emusubdirectory containing the platform-specific source for the host platform.Each library has its own.CW mkfile ;the various components are made in the right order by the.CW mkfileat the root of the Inferno tree.The.CW mkfilefor each platform will also invoke.CW mkrecursively to make the appropriate librariesfor a given configuration..PPThe Unix emu variant generally is covered by `POSIX' (with common extensions)but each Unix port has one file that differs considerably for each port,namely \f5emu/\fP\fIplatform\fP\f5/os.c\fP, the differencescorresponding to the different ways under Unix of implementing kernel-scheduledthreads efficiently..PPThere are working emu versionsforFreeBSD/386,Irix/mips,Linux/386,NetBSD/386,MacOSX/386,MacOSX/power,Plan 9,Solaris/sparc,and Windows (NT, 2000 and Explorer plug-in).Each platform typically uses mechanisms specific to the host operatingsystem to implement Inferno's internal thread/process structure.POSIX threads have often been found to be insufficient (poorly implemented)on some platforms, and if so are avoided.See.CW kprocin.CW emu/*/os.c ..PPSource is included for ports to HP/UX (S800 architecture),Solaris/386, and Unixware, in case someone wishes to take them up now,but we have not determined their fitness..PPThe Plan 9 hosted implementation is unusual in that it supportsseveral processor types:.CW 386 ,.CW mips ,.CW power(Power PC)and.CW sparc .Furthermore, all versions of.CW emucan be built on any processor type, in the usual way for Plan 9..PPOtherwise, as distributed,.CW emufor a platform can only be built when running on that platform..PPOne unusual variant makes the whole of Inferno a plug-in for Microsoft'sInternet Explorer, giving the same environment for Inferno applicationsrunning in an HTML page as is provided by hosted or native Inferno.That is, there is not a distinct `applet' environment with special programming interfaces.The source for the various plug-in components is found in.CW /tools/pluginand.CW /usr/internetwithin the Inferno tree; they use the version of.I emudefined by the configuration file.CW /emu/Nt/ie ..SHBuild steps.PPAll the libraries and executables can be built in a tree containing only the source code.To do that for a supported variant of hosted Inferno, on Unix or Plan 9, do the followingin the root of the Inferno tree:.nr Ci 0 +1.de Xx.IP \\n+(Ci...XxEdit.CW mkconfigto reflect your host environment,specifically ROOT (which must be an absolute path name), SYSHOST and OBJTYPE.The comments in the file should help you choose..XxRun.CW makemk.shto rebuild the.CW mkcommand, which is used to build everything else..XxSet.CW PATH(or.CW pathon Plan 9)to include the.CW bindirectory for the platform, which will now contain the.CW mkbinary just built.On Unix, export.CW PATH ..XxThen.CW "mk nuke"to remove any extraneous object files..XxFinally,.CW "mk install"to create and install the libraries,.CW limbocompiler,.CW emufor hosted Inferno, and auxiliary commands.The rules do that in an order that ensures that the commands or librariesneeded by a later stage are built and installed first.(Note that a plain.CW mkwill not suffice, because it does not put the results in the search path.).LPDoing something similar on Windows or Plan 9 currently requires the executable for.CW mkto be available in the search path,since there is no equivalent of.CW makemk.sh .Otherwise the procedure is the same.On Plan 9, of course, the host system's normal version of.CW mkshould be adequate.