Scribd
Upload
41 views

System and Network Administration GCC & Make

This document discusses system and network administration topics such as: 1. It describes Linux distributions, source code, binary files, dependencies, and packages. It also discusses different package managers like apt-get, yum, and pkgtool. 2. It explains shared libraries and dynamic link libraries, how they are loaded into RAM and managed by the kernel. It discusses library dependencies. 3. It provides an overview of compiling software from source using gcc and make. It mentions the essential components of a Linux distribution and discusses building software on different distributions and versions.

Uploaded by

Arsalan Jahani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
41 views

System and Network Administration GCC & Make

This document discusses system and network administration topics such as: 1. It describes Linux distributions, source code, binary files, dependencies, and packages. It also discusses different package managers like apt-get, yum, and pkgtool. 2. It explains shared libraries and dynamic link libraries, how they are loaded into RAM and managed by the kernel. It discusses library dependencies. 3. It provides an overview of compiling software from source using gcc and make. It mentions the essential components of a Linux distribution and discusses building software on different distributions and versions.

Uploaded by

Arsalan Jahani
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

System and Network Administration

gcc & make


Source and Packages

• A Linux distribution is a collection of utilities bundled around


the Linux kernel.
• Source code is the program in text file format, usually written
in the language C
• A binary file is the result of compiled source code.
• A dependency is a component of the system that must
already be installed before another program will function.
– Some, but not all, compilation scripts will attempt a
dependency check prior to installation.
• Packages are pre-configured binary files for specific
distributions.

System & Network Administration


Source and Packages
Package managers keep track of which packages have been
installed, and perform a dependency check when you install
software
Some distributions offer a tracking service that will notify you when
new versions of installed packages are available.
Others automatically download packages from an official repository

Debian/Ubuntu RedHat Slackware


Local – dpkg Local – rpm Local – pkgtool Celebrate
Diversity!
Auto – apt-get Auto – yum Auto – (none)

TinyNet: mount SlaxArchive CD

System & Network Administration


Shared Libraries (.so)
Dynamic Link Libraries (.dll)

• Loaded into RAM on demand


• Managed by some kernel routines which use an “index” to
locate a required module
Special command used to do this – ldconfig
• Must have the right libraries on your system
dependencies – missing or wrong version, cannot start
packages – bundle libraries, but often depend on others
package managers – help sort out dependencies

It is very likely that you will actually need to


configure these, for one application or another

System & Network Administration


Compiling: gcc & make

• There are four essential ingredients in a Linux distribution: the


kernel code, the C compiler, C libraries, and the binutils package
(the linker and other build tools).
• While there are exceptions, because some applications depend
on certain features in the C libraries or the kernel (newer versions
of the monkey webserver, for example), in general any code you
can compile will work.
• Binaries other versions and distributions are highly likely to work,
when the versions of their major components are similar.
• distrowatch.com tracks the characteristics of about a zillion
distributions, but there are only 3 major ones to keep an eye on:
Slackware, Ubuntu (Debian), and Redhat (CentOS).

System & Network Administration


make, cmake, automake

• In these modern times we usually get software from a repository,


but sometimes you need to compile it for yourself.
• make (or rather a Makefile) is a buildsystem - it drives the
compiler and other build tools to build your code.
• If you intend your project to be multi-platform or widely usable,
you really want a buildsystem generator
• CMake (cross-platform make) can produce Makefiles, Ninja build
files, KDEvelop or XCode projects, and Visual Studio solutions
from the same starting point, the CMakeLists.txt file
• GNU Autotools (automake) integrate very well with building Linux
distributions. They are not a general build system generator -
they implement the GNU coding standards and nothing else.

System & Network Administration


• Make, Cmake, and GNU Autotools are actually insanely
complicated, but they make the build process practically painless.
• Essentially, each application will have a makefile with various
targets – some common ones are
– make
– make install
– make clean

• There may be a layer “above” the makefile: Cmake or configure


(GNU Autotools).
• We can add another layer to automate even more: SlaxBuild

System & Network Administration


The basic process is:

• Use mc to copy the top directory for the source code from the
archive file into /opt
• Switch to /opt, move down one level to the source code
– Look for configure – this one uses automake
– Look for CMakeLists.txt – this one uses Cmake

System & Network Administration


The basic process is:

• IF you have a package that uses Automake or Cmake, THEN

– Copy Template.SlaxBuild to another directory, rename it


app.SlaxBuild, and copy it back to the same directory as
the source code archive.
– Follow the instructions there to make the necessary edits
and customisations
– Run ./app.SlaxBuild. If everything works, it will create two
new files and install the application

System & Network Administration


The basic process is:

• IF you do not have a package that uses Automake or Cmake,


THEN
– Check the Makefile for options you can customise
– Check the Makefile for an INSTALL target and CLEAN
– Check the Makefile for a CLEAN

• Run make. If everything works, it will create new files in the


source directories
• If you can, run make install to move the new files from the
source directories into their proper places in the filesystem
• If something goes wrong, run make clean to remove new files
from the source directories, debug, and run make again

System & Network Administration


Study the SlaxBuild to see what it is doing

See TinyNet Images: ReadMe on the website to get a gcc VM set up

System & Network Administration


System & Network Administration

You might also like