install.txt 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103
  1. INSTALL(1) INSTALL(1)
  2. NAME
  3. install - notes about Plan 9 from User Space installation
  4. SYNOPSIS
  5. cd /usr/local/plan9; ./INSTALL [ -b | -c ] [ -r path ]
  6. DESCRIPTION
  7. To obtain the Plan 9 tree, use Git (see git(1)) or download
  8. a tar file from https://9fans.github.io/plan9port.
  9. The tree can be unpacked anywhere, but the usual place is
  10. /usr/local/plan9. In the root of the tree, run ./INSTALL.
  11. This script builds the Plan 9 build program mk(1) if neces-
  12. sary, cleans all previously built object files and libraries
  13. out of the tree, rebuilds and installs everything, and then
  14. cleans up.
  15. There are a few files in tree which have the root hard-coded
  16. in them. After the build, INSTALL edits these files to
  17. replace the string /usr/local/plan9 with the name of the
  18. root of the current tree.
  19. Finally, INSTALL builds an HTML version of the manual and
  20. installs it in /usr/local/plan9/man.
  21. The installation can be thought of as two steps: build all
  22. the binaries, and then edit files as necessary to fix the
  23. references to the installation root. If necessary, these
  24. can be run separately. Given the -b flag, INSTALL performs
  25. only the first step. Given the -c flag, INSTALL performs
  26. only the second step. The first step can be done with the
  27. tree in a temporary work directory, but the second step must
  28. be done once the tree is in its final location. If you want
  29. to build the project in one location and then install into
  30. another location, use -r path to specify the final location
  31. of Plan9 tree. These flags are only necessary when trying
  32. to conform to the expectations of certain package management
  33. systems.
  34. At the end of the installation, INSTALL prints suggested
  35. settings for the environment variables $PLAN9 and $PATH.
  36. INSTALL writes various autodetected settings to
  37. /usr/local/plan9/config. The file
  38. /usr/local/plan9/LOCAL.config is appended to config after
  39. this auto-detection and can be used to override the choices.
  40. If LOCAL.config contains a line WSYSTYPE=nowsys then the
  41. system is built without using X11. LOCAL.config may also
  42. list settings for CC9 (the host C compiler) and CC9FLAGS
  43. (any additional flags to pass to the compiler). Values more
  44. Page 1 Plan 9 (printed 4/9/21)
  45. INSTALL(1) INSTALL(1)
  46. complex than single words should be quoted with single
  47. quotes.
  48. On most Linux systems, the X11 header packages need to be
  49. installed to build using X11. On Debian. the required pack-
  50. ages are libfontconfig1-dev, libx11-dev, libxext-dev, and
  51. libxt-dev. On Ubuntu, it suffices to install xorg-dev.
  52. INSTALL can safely be repeated to rebuild the system from
  53. scratch.
  54. Once the system is built for the first time, it can be main-
  55. tained and rebuilt using mk(1). To rebuild individual com-
  56. mands or libraries, run mk install and mk clean in the
  57. appropriate source directory (see src(1)).
  58. FILES
  59. /usr/local/plan9/lib/moveplan9.files
  60. the list of files that need to have /usr/local/plan9
  61. edited out of them
  62. /usr/local/plan9/lib/moveplan9.sh
  63. the script that edits the files
  64. /usr/local/plan9/src/mkmk.sh
  65. the shell script used to build mk(1)
  66. /usr/local/plan9/dist/manweb
  67. the shell script that builds the HTML manual
  68. /usr/local/plan9/man/index.html
  69. the top-level page in the HTML version of the manual
  70. /usr/local/plan9/install.log
  71. logged output from the last run of INSTALL
  72. /usr/local/plan9/install.sum
  73. a summary of install.log
  74. SEE ALSO
  75. intro(1), git(1)
  76. Page 2 Plan 9 (printed 4/9/21)