Difference between revisions of "SPO600 Code Building Lab"

From CDOT Wiki
Jump to: navigation, search
Line 15: Line 15:
 
# Build the software. You may need to install build dependencies (e.g., compilers, tools, and libraries); you can do this (and only this) as the root user.
 
# Build the software. You may need to install build dependencies (e.g., compilers, tools, and libraries); you can do this (and only this) as the root user.
 
# Test that it works.
 
# Test that it works.
# Select a second, open source software package that has a different license, and repeat the process with that software.
+
# Find and build the source code for the latest released version of the GNU Standard C Library (glibc). Test the library which you have built (Critical: do this without installing it on your system and overwriting your existing glibc installation!). Prove that your version of the library is used in your tests.
 
# Blog about the process, your results, your observations, and what you learned.
 
# Blog about the process, your results, your observations, and what you learned.

Revision as of 23:23, 27 August 2017

Lab icon.png
Purpose of this Lab
In this lab, you will do a baseline build of a software package.

Lab 2

Prerequisites

You must have a working accounts on a Linux system (such as Matrix, Zenit, the SPO600 Servers or your own system).

Tasks

Stop (medium size).png
Do not build or install this software as the root user.
Do not build the software as root, and do not install the software into the system directories. Doing so may cause conflicts with other software on the system and/or may leave your system in an unusable state, and may be very difficult to reverse.
  1. Select a software package from the Free Software Foundation's GNU Project.
  2. Download the source code for the software.
  3. Build the software. You may need to install build dependencies (e.g., compilers, tools, and libraries); you can do this (and only this) as the root user.
  4. Test that it works.
  5. Find and build the source code for the latest released version of the GNU Standard C Library (glibc). Test the library which you have built (Critical: do this without installing it on your system and overwriting your existing glibc installation!). Prove that your version of the library is used in your tests.
  6. Blog about the process, your results, your observations, and what you learned.