Page Template

Jump to navigationJump to search
Download Source: URL
Download Patch: URL - This should be a URL beginning with See for instructions on submitting patches for CBLFS.

Introduction to Page Template

Brief description of the package you are enlightening us with. Try to provide a description in your own words. Add a link to the package's homepage for someone unfamiliar with the package to research further.

Project Homepage: http://homepage/to/cool/package

If there is some reason you are adding a package and are unable to provide a brief description of it's functionality, please do two things. First, reconsider installing software that you have no idea what it does. Second, please use this template. It allows us to identify packages that need introductions without "hunting" through the wiki.

Introduction to Page Template

Project Homepage: Unknown

Use this template to add notes where ever a note is appropriate.





If there are no dependencies, omit this section.





Creating the <NAME> User & Group

This is an optional section. If your package requires a user/group add this section to the page then append the table on the System User and Groups page. Below is an example. If there is no need to create a user or group, omit this section.

groupadd -g [id] [name] &&
useradd -c "[desc]" -d /dev/null \
       -u [id] -g [name] -s /bin/false [name]

Configuration Information

This section can contain options that you may want to include when configuring the package, but should be left as a choice. However, don't just reproduce the output of ./configure --help; be judicious in your selection. If there are no configuration options that warrant discussion, omit this section.

--enable-someoption: brief description of the non-default functionality provided by someoption.
--disable-someotheroption: brief description of the default functionality removed by disabling someotheroption.

Generally speaking, CBLFS packages are installed in the /usr hierarchy although there are some exceptions. Even if you passed --prefix=/home/fubar/stuff/CBLFS/is/really/awesome/some/package/version/5.0/hope/this/works to the configure script, please use --prefix=/usr for the wiki. Thanks. Also, the instructions presume that the source package has been retrieved to the local machine, unpacked, and you have cd'd to the top of the source tree. Generally, we don't need those instructions unless there is something very unique about the process for the package you are adding.


Compile the package:

./configure --prefix=/usr &&

Install the package:

make install


If appropriate, add this line and only include the 64-bit instructions:

This package does not provide any libraries or other ABI-specific information so only one installation is required.

If package documentation is not installed by the 'make install' step, only include the commands to install the documentation in the 64-bit section.


Compile the package:

CC="gcc ${BUILD32}" ./configure --prefix=/usr &&

Install the package:

make install


Compile the package:

CC="gcc ${BUILDN32}" ./configure --prefix=/usr \
    --libdir=/usr/lib32 &&

Install the package:

make install


Compile the package:

CC="gcc ${BUILD64}" ./configure --prefix=/usr \
    --libdir=/usr/lib64 &&

Install the package:

make install


This section should contain information about the post-installation configuration of a package, bootscript(s), other files, creating directories. Omit this section if there is no post-installation configuration required.


You can find an application here that can be used to make creating this table reasonably pain free.

Installed Directories: /path/to/dir
Installed Programs: Program 1, Program 2
Installed Libraries: library1.{a,so}, library2.{a,so}

Short Descriptions

Program 1 is a program that converts pennies to dollars.
Program 2 is a program that converts dollars to pennies.
library1.{so,a} is a library that contains functions necessary to convert from dollars to pennies and vice versa.

[[Category:<PUT APPROPRIATE CATEGORY HERE>]] See for a list of categories. Likely your package will fit in one of the existing categories. If not, and think long and hard about it, create a new category.