Difference between revisions of "SPO600 Code Building Lab"
Chris Tyler (talk | contribs) |
Chris Tyler (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | [[Category:SPO600 Labs]]{{Admon/lab|Purpose of this Lab|In this lab, you will do a baseline build of a software package.}} | + | {{Chris Tyler Draft}}[[Category:SPO600 Labs]]{{Admon/lab|Purpose of this Lab|In this lab, you will do a baseline build of a software package.}} |
== Lab 2 == | == Lab 2 == | ||
Revision as of 14:47, 10 September 2017
This is a draft only!
It is still under construction and content may change. Do not rely on this information.
It is still under construction and content may change. Do not rely on this information.
Purpose of this Lab
In this lab, you will do a baseline build of a software package.
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
.png){kind=small}
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.
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.
- Select a software package from the Free Software Foundation's GNU Project.
- Download the source code for the software.
- 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.
- 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.
