Difference between revisions of "SPO600 Code Building Lab"
Chris Tyler (talk | contribs) |
Chris Tyler (talk | contribs) (→Tasks) |
||
Line 11: | Line 11: | ||
{{Admon/caution|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.}} | {{Admon/caution|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.}} | ||
− | # Select | + | # Build an open source software package |
− | # Download the source code for the software. | + | ## Select an open source software package from the [http://www.gnu.org/software/software.html Free Software Foundation's GNU Project] or another open source project. |
− | # 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. | + | ## Download the source code for the software. (Do not install with dnf/yum!) |
− | # Test that it works. | + | ## 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. |
− | # 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. | + | ## Test that it works. |
− | # Blog about the process, your results, your observations, and what you learned. | + | ## 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. | ||
+ | # Build and test glibc | ||
+ | ## Obtain the source code for glibc via git using the instructions at https://sourceware.org/glibc/wiki/Testing/Builds | ||
+ | ## Build and test your version of glibc. '''Do Not''' install it into the system directories or you may destroy the existing Linux installation! |
Revision as of 20:48, 10 September 2017
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
- Build an open source software package
- Select an open source software package from the Free Software Foundation's GNU Project or another open source project.
- Download the source code for the software. (Do not install with dnf/yum!)
- 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.
- Build and test glibc
- Obtain the source code for glibc via git using the instructions at https://sourceware.org/glibc/wiki/Testing/Builds
- Build and test your version of glibc. Do Not install it into the system directories or you may destroy the existing Linux installation!