Chris Tyler's Wiki

User Tools

Site Tools

Trace: • 64-bit_assembly_language_lab • 6502_assembly_language_lab
spo600:building_gcc

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
spo600:building_gcc [2025/01/31 14:51] – [Step 0: Decide Where to Build] chrisspo600:building_gcc [2025/01/31 15:14] (current) – [Step 3: Perform the Build] chris
Line 43: Line 43:
 Once you have configured the build, you can use ''make'' to perform the build. By default, make will only start one job (subprocess, such as gcc) at a time. You can use the ''-j'' option to specify the maximum number of jobs which make will execute simultaneously; the value provided to ''-j'' should be in the range of (number of cores + 1) to (number of cores * 2 + 1) -- use the higher end of this range for machines with hardware multi-thread support (aka hyperthreading) or slow disk systems, and the lower end of this range for machines without multi-thread support. Once you have configured the build, you can use ''make'' to perform the build. By default, make will only start one job (subprocess, such as gcc) at a time. You can use the ''-j'' option to specify the maximum number of jobs which make will execute simultaneously; the value provided to ''-j'' should be in the range of (number of cores + 1) to (number of cores * 2 + 1) -- use the higher end of this range for machines with hardware multi-thread support (aka hyperthreading) or slow disk systems, and the lower end of this range for machines without multi-thread support.
  
-Before building, consider that the build may take anywhere from 20 minutes to several hours depending on the build options, speed of the build computer, and what else is being done on the computer (e.g., multiple builds by several users). It is strongly recommended that you use the [[screen]] utility (or similiar tool) to permit disconnection and reconnection if needed.+Before building, consider that the build may take anywhere from 20 minutes to several hours depending on the build options, speed of the build computer, and what else is being done on the computer (e.g., multiple builds by several users). It is strongly recommended that you use the [[Screen Tutorial|screen]] utility (or similiar tool) to permit disconnection and reconnection if needed.
  
 It is also recommended that you record the time taken for the build to complete using the shell built-in ''time'' command, and that you redirect the stdin and stdout to a log file as well as the screen using the ''tee'' program. It is also recommended that you record the time taken for the build to complete using the shell built-in ''time'' command, and that you redirect the stdin and stdout to a log file as well as the screen using the ''tee'' program.
Line 73: Line 73:
 ===== Things to Watch For ===== ===== Things to Watch For =====
  
-  * Be aware of who else is using the build computer and what they're doing on it. Use command such as ''w'' or ''who'' as well as  ''top'' or ''btop''.+  * Be aware of who else is using the build computer and what they're doing on it. Use commands such as ''w'' or ''who'' as well as  ''top'' or ''btop''.
   * Be aware of available disk space (''df -h .'')   * Be aware of available disk space (''df -h .'')
-  * Keep an eye on currently-available memory (''free'' -- watch the "Available" memory, not the "Free" memory)+  * Keep an eye on currently-available memory (Use the command ''free'' -- watch the "Available" memory, not the "Free" memory)
  
spo600/building_gcc.1738335101.txt.gz · Last modified: 2025/01/31 14:51 by chris
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki