Linux Foundation Wiki

project collaboration site

User Tools

Site Tools


Porting to the LSB Demo

Note: This article is out of date in some places, but is kept for posterity.

Because Linux is an open operating system, you can configure and assemble it to suit specialized purposes. However, while variety and choice are beneficial for users, heterogeneity can vex software developers who must build and support packages on a multitude of similar but subtly different platforms. Fortunately, if an application conforms to the Linux Standard Base (LSB) and a flavor of Linux is LSB compliant, the application is guaranteed to run. Discover the LSB, and learn how to port your code to the standard.

This tutorial describes the Linux Standard Base (LSB), a specification and collection of tools and test suites that help Linux software developers increase compatibility among Linux software distributions. Applications and distributions can be certified compliant with the specification, providing assurances to users that certified software is compatible. This tutorial describes the LSB and explains how to vet your application code to conform with it.


To benefit from this tutorial, you should have experience with the C or C++ programming language as well as the typical Linux software development environment and its cadre of tools, including the compiler, linker, system libraries, configuration and build utilities, and packaging tools.

You should also have experience installing software from the command line and have at least a modicum of experience with administering and maintaining a Linux system, such as configuring a file system, starting and stopping network services, and adding system services.

If you're running Debian Linux, you should also have some experience with the APT package manager.

Before you start the tutorial, you must install several software packages on your Linux system. Here's everything you need:

  • The KVM package for your Linux distributionNote: Alternatively, you can easily install VMWare Workstation on any computer running Microsoft Windows XP and run a virtualized Linux instance on the Windows XP platform. Download a trial version of VMWare Workstation at no cost and use it to create one or more virtual machines (VMs). After you've created a VM, you can save it and switch to the free VMWare Player to replay it.

You may also find it useful to download and read the LSB V4.0.0 specification appropriate for your target hardware platform. Hardware-specific LSB specifications are available for seven popular architectures: the IA32, IA64, PPC32, PPC64, S390, S390X, and AMD64 processors.

If you want to certify your application, please visit the Linux Foundation's “Certifying an Application to the LSB.”

To run the examples in this tutorial, you must have a computer running either the Linux or Windows XP operating system. VMWare Workstation running on either of those platforms provides a Linux environment for you to do the rest of your work.

If your application depends on software libraries other than those ratified as part of the LSB specification for your processor, you must install those libraries on the virtual system, as well. To avoid confusion, it's ideal to install application-specific libraries separately from the standard libraries.

The Need for a Standard

According to the DistroWatch Web site, at least 25 significant Linux distributions currently exist. If you include other variations – some optimized for size (such as Damn Small Linux), some for convenience (such as Knoppix), some tailored to a specific audience (such as Fedora Core), and still others customized for a specific country (such as Red Flag Linux)–that rather staggering number of choices easily doubles or triples. Linux is the only modern operating system with such numerous variations.

On one hand, the do-it-yourself culture of Linux encourages diversity and specialization. On the other hand, such proliferation can be overwhelming, especially if you're an independent software vendor (ISV) faced with developing, selling, and supporting a Linux application. If the “UNIX Wars” of the 1980s splintered ISVs' chances of success, so many Linux versions seem to promise nothing less than wholesale obliteration of the market for rich Linux applications. To wit, imagine the expense of building and supporting a complex application on more than a handful of Linux variants.

LSB Terminology

When discussing the LSB, you'll frequently hear (and read) the terms conformance, compliance, and certification:

  • The LSB defines requirements for a run time and an application to be in conformance with the specification.
  • An application or a distribution is in compliance with the LSB if its developer has realized all the suitable LSB requirements and claims that the software conforms.
  • An application or distribution receives certification if it successfully demonstrates compliance through official review.

In this tutorial, you learn how to create compliant applications. You cannot self-certify your application, although you can run many tests that greatly increase the likelihood of certification.

Promoting Interoperability

In an attempt both to encourage diversification and provide consistency, the Free Standards Group (now The Linux Foundation) created the Linux Standard Base, an “open source project to develop and promote a set of standards [to] increase compatibility among Linux distributions and enable software applications to run on any compliant system” (according to the LSB Web site).

Specifically, the LSB defines a consistent Linux platform. A Linux distribution is LSB compliant if it implements (at least) the LSB platform. (Nothing precludes a version of Linux from providing additional features.) A Linux application is LSB compliant if it consumes only the services that the LSB platform provides. If the application requires additional libraries, it provides those, either during installation or through static linking. (Of course, the libraries must be self-sufficient and LSB compliant, as well.) The sidebar “LSB terminology” explains what other terminology means.

The figure below shows the many areas for which the LSB defines (or will eventually define) standards. The areas are libraries, the basis of all Linux applications; the execution environment, including mandates for where certain critical system files reside and how the system provides for localization services; system initialization; common commands and utilities to be found across all LSB-compliant systems; and user and group management. Figure 1. The Components of the LSB

Application developers are probably most concerned with the blue and orange boxes.

In blue, the LSB stipulates a set of core libraries and additional modules that an LSB-compliant application can use. The core libraries include libc, libm, libpthread, libpam, libcrypt, libz, libncurses, librt, and libgcc_s. Modules include a module for X Window System Version 11 graphics (libX11, libXt, libXext, libSM, libICE, and libGL) and the C++ standard library, libstdc++.

In orange–and not part of the LSB specification–is a set of valuable companion tools to validate that applications, packages, (and soon, static libraries) are LSB compliant.

Binary Compatibility

The LSB specification is a binary compatibility standard. An application binary (compiled, executable code) that is LSB compliant can run unchanged on any LSB-compliant Linux distribution (built for the same processor architecture as the application).

Binary compatibility is remarkably different from source compatibility. An application that is source compatible requires the software to be recompiled in situ, with the local system's compilers and libraries–two significant founts of variability and unpredictability. Source compatibility doesn't guarantee that the executable will run, let alone run as expected.

The Benefits of Consistency

Think of the LSB as a kind of binding agreement between a distribution and an application. The distribution “agrees” to provide (at least) the specification's libraries and interfaces, and the application “agrees” to use only those libraries and interfaces, providing any other software that's needed. To ensure that “both parties” adhere to the agreement, the LSB provides tools, guidelines, and validation services to certify Linux distributions and applications as LSB compliant.

Adherence to the LSB inures to the benefit of distribution vendors, ISVs, and users alike.

For the distribution vendor:

  • A distribution vendor can promote compliance with the LSB, assuring customers that LSB compliant applications will run consistently and reliably on its product.
  • After its distribution is certified LSB compliant, a vendor can re-focus its energies on differentiating, novel features.

For the ISV:

  • An application developer can create and certify a single binary and deploy it to any LSB-compliant distribution.
  • An ISV need only test and support the single, certified binary. Additionally, if the binary is sufficiently internationalized, a single version of an application might suffice for all customers, independent of nationality.

For the customer, the user:

  • The user can pick and choose among competing LSB-compliant distributions, either to deploy the most appropriate flavor of Linux or to avoid vendor lock-in.
  • The user has many Linux applications to choose from.

Given all the dynamics listed above, distribution vendors, ISVs, and users reap rewards from each unique investment in Linux. In turn, Linux benefits, as well.

The LSB Build Environment, SDK, and Sample Implementation

The LSB is a “contract” between an application and a distribution to adhere to the LSB specification. Ignoring the complications of making a Linux distribution compliant, how can a Linux application developer–you–ensure compliance?

If you're a developer, you likely know your code very well and can work diligently to meet the obligations of LSB compliance. However, it may not always be obvious that your code depends on a non-standard (non-LSB) component, especially as a typical Linux distribution has thousands of components strewn about the system.

For example, perhaps your code depends on a non-compliant string library found only on your favorite distribution. Or perhaps, the string library used was added locally and recently by your system administrator. As an another example, perhaps your code depends on a specific version of a library. Version W of the library is LSB compliant, but version Y–the version you depend on–is not part of the LSB specification.

Tools to Help You Migrate

To help find and remove such dependencies–the crux of making your code LSB compliant–the LSB provides two significant tools: the Build Environment and the Sample Implementation.

The Build Environment helps you identify source code that depends on non-LSB libraries and application binary interfaces. The Build Environment consists of header files, stub libraries, and a compiler wrapper that simulate a software build environment on a compliant Linux system. You can install the Build Environment on any Linux system–even one that is not compliant.

The SDK is a set of stub libraries, headers, and a wrapper for the system compiler that run within your local operating system. The SDK allows compliant builds within an LSB environment. 

The Sample Implementation helps you validate that your application executes successfully in a compliant run time environment. You can think of the Sample Implementation as a mini-Linux (yes, you can boot from it, if you want to)–an environment that proxies for an LSB-compliant distribution.

Of course, you could use an LSB-compliant distribution as your test environment, but the Sample Implementation has a few advantages: It only includes what's defined in the LSB, and several versions of the Sample Implementation exist–one each for version of the LSB specification. Hence, if you want to verify that your application is LSB V3.0 and LSB V3.2 compliant, you can install the respective Sample Implementations on a single test system rather than require two Linux systems. Certainly, the Sample Implementation is the preferred method to validate your application against a newly ratified LSB specification before real-world, compliant systems are available.

An individual Build Environment and Sample Implementation set is provided for each version of the LSB standard. For this tutorial, you'll use LSB V4.0.0 as the target platform. (Version 4.0 was the most recent LSB specification at the time this tutorial was written. Versions 3.2.0, 3.1.0, and 3.0.0 are previous versions of the LSB. You'll likely find that many popular Linux distributions are certified with either of the earlier instances of the LSB.)

Since LSB V4.0.0, the SDK is not bound to a particular specification version and can be used to create applications compatible with any given LSB version greater or equal to 3.0.0. By default, the latest LSB version is used as a target. To change target version, one should use either LSBCC_LSBVERSION environment variable or '–lsb-target-version' option of the compiler wrapper. 

The Benefits of Porting Using Virtual Machines

To run the LSB V4.0.0 Sample Implementation, you need an operating system capable of running the Sample Implementation in a chroot environment. The community distribution openSUSE 11.1 is one flavor of Linux that can run the V4.0 Sample Implementation, which we will use for the purpose of this tutorial.

But what if you don't have OpenSUSE installed? Or, what if you want to run your application on numerous instances of the LSB or on a handful of Linux distributions? You could assemble a (somewhat large) collection of hardware or multi-boot among all your desired variations, but a far easier and less-expensive solution is to run each Linux distribution in its own VM.

KVM is a virtualization technology which is supported on most modern distributions, including Ubuntu Hardy. It does require a relatively new x86 CPU that supports the Intel-VT or AMD-V (also called the AMD SVM extensions). A list of which CPU's support (or do not support) these extensions can be found on this web page maintained by Xensource. On some systems, the virtualization extensions have to be enabled via a BIOS configuration awitch, and may require a complete power cycle after changing the BIOS configuration and saving the configuration to flash.

If your Linux system does not support KVM, or if you wish to run this tutorial on non-Linux sytem, such as a Windows XP system, it is possible to download and install VMWare instead. VMWare is available in at least 3 different configurations: Player, Server, and Workstation. Both VMWare Player and Server are available as a free download, while VMWare Workstation requires a license. You can then use one of the LSB's “appliance” images of the Sample Implementation to follow the rest of this demo.

Download and Install VMWare

Install VMWare on Debian Linux, and run the LSB V4.0 Sample Implementation in a VM.

Download a VM Image

The LSB Workgroup provides the Sample Implementation integrated into a virtual appliance that runs openSUSE 11.1 as the host OS. There are two variations on this appliance: “si” and “siX”. The former is a console only variation that boots you directly into the SI, while the latter provides an X environment with the SI running in a terminal window. The SI applance images are currently in beta, available here and can be run with qemu or vmware.

Installing KVM

If you are running Ubuntu Hardy system, installing is as simple as installing the KVM package. This can be done by using the command:

sudo apt-get install kvm

in a terminal window. Or, you can use the Synaptics package manager if you prefer using a graphical interface.

As packaged in the Debian and Ubuntu distributions, in order to use kvm without being root, your user id must be in the “kvm” group. You can edit the /etc/group via a text editor as the superuser, or if you are running Ubuntu, you can use the menu selection System→Administration→Users and Groups from the system's menubar, and then on the click on the “Unlock” button, enter your password, then click on “Manage Groups”. This will cause a “Group Settings” window to appear. Find “kvm” in the selection window, and then click on “Properties”, and then add a check-mark next to your user id in the “Group Members” list, and then click the “OK” button. After you make a change to the group membership of the “kvm” group, you will need to logout and then login again so the change can take effect.

Running KVM

To start the KVM virtual machine you simply untar the lsb-siX-vm tarball and run the following command in a terminal window:

kvm lsb-siX-vm-4.0.1-2.i686-1.1.2.vmdk

The KVM application traps all mouse and keyboard input unless you press Ctrl+Alt. To set the focus back to the virtualized environment, just click in the KVM window. There are additional arguments mentioned in the README that comes with the lsb-siX appliance that allow networking and port redirection to move files in and out of the virtual machine.

Congratulations! You now have openSUSE 11.1 running in its own VM!

Porting Your Code to the LSB

With setup behind you, you can begin the process of porting your code to the LSB.

The General Approach to Porting

Porting an application to the LSB requires the following steps:

  1. Copy your code to the new build system.The new build system might be an LSB-compliant Linux distribution running on separate hardware or, in this case, a VM.
  2. Build your code, and run the Linux Application Checker (“AppCheck”) tool to scan your binary for symbols that are not expressly provided in the LSB specification.You can also this tool to scan your static archives for suitability for use in an LSB-compliant application.
  3. If AppCheck finds invalid symbols, change your code or the assembly of your code to bring it into compliance.For instance, if you're using a library that isn't part of the LSB specification, link to it statically so that the code is self-contained in your binary. (Again, this assumes that the code in the library itself is otherwise LSB compliant.) Assuming that you've addressed all the issues, you can proceed to the next step.
  4. Use the LSB Build Environment to build the code in a clean, compliant environment.If your code uses libraries that are not provided for under the LSB, you must modify your build process to either install or link statically to those libraries. (Remember that all libraries must be LSB compliant, as well.)
  5. If your code builds successfully within the LSB Build Environment, run the code in the LSB Sample Implementation.


  1. If your target Linux system is LSB compliant, run your code on that system.


  1. Package your application.LSB-conforming systems promise to be able to install an LSB-compliant RPM. However, you need not limit yourself to that format, with the caveat that the packaging technology you choose must work on an LSB-compliant system. For example, a compliant shell script with a tarball is an acceptable format. Your own installer is acceptable, too, as long as the installer itself is LSB compliant.

Now, let's build a simple application to elaborate on the process.

Installing and Running the LSB Build Environment Utilities

Before using the chroot version of the LSB Build Environment, try the Build Environment utilities, which you can quickly and easily install on virtually any Linux system. You can use the Build Environment utilities lsbappchk and lsbpkgchk to quickly determine why your application and RPM package (the standard LSB format), respectively, aren't compliant with the LSB.

Download and Install the Build Environment Utilities

The Build Environment utilities are available as two RPMs, one for lsbappchk and another for lsbpkgchk. Because the test system is Debian Linux, you can either convert the RPMs to DEB format using alien, or download the native .deb packages suitable for Debian's dpkg package manager. For a more complex application, with a GUI, you may want to also download lsb-build-desktop, lsb-build-qt3 and/or lsb-build-qt4.

1 $ sudo apt-get install wget
2 $ wget
3 $ wget

4 $ wget
5 $ wget
6 $ wget

7 $ wget
8 $ sudo apt-get install alien
9 $ alien -k *.rpm
10 $ ls -t -1 *.deb
11 $ sudo dpkg --install *.deb
12 $ ls /opt/lsb
bin  doc  man
13 $ ls /opt/lsb/bin
lsbappchk  lsbc++  lsbcc  lsbpkgchk

The native .deb packages are at:

Command 1 installs wget if it isn't already available on the system. Commands 2-7 download the latest versions of the LSB utilities:

  • lsb-appchk verifies that a supplied binary only uses the dynamically linked symbols defined in the LSB.
  • lsb-pkgchk verifies that an application package–a bundle used to install the software on an LSB-compliant system–is valid. The lsb-pkgchk tool is intended for RPMs only. However, the LSB does not mandate the use of RPMs to install software.
  • lsb-setup simply provides the /opt/lsb/* directory structure used by a number of lsb packages
  • lsb-build-base provides stub libraries and header files. While the stub libraries don't implement the functions defined in the LSB, they do mimic the actual dynamic libraries found on an LSB system. Hence, you can use lsb-build-base to build a compliant application.
  • lsb-build-c++ adds C++ support to the build environment.
  • lsb-build-cc contains lsbcc, a wrapper around the GNU Compiler Collection (GCC) compiler that yields LSB-conforming applications. If your application uses a GNU-style configure script, you can easily modify your script to use lsbcc instead of the default system (typically GCC) CC compiler. In some cases, you can directly replace GCC with lsbcc (for example, in a makefile).

Command 8 installs alien, a utility that can convert RPMs to Debian DEB packages (among other features). Command 9 runs alien; command 10 shows the results; and command 11 installs all the software into the /opt/lsb/ directory, as shown in commands 12 and 13. If you use the native .deb packages, steps 8 and 9 would be skipped.

If your system supports a package manager such as apt, yum, or zypper, you can also add LSB package repositories and install the SDK and application tests using those tools. The LSB repositories are at:

A typical entry in the /etc/apt/sources.list file would look like:

deb lsb-4.0 main

For yum would would create an LSB repo file like /etc/yum/repos.d/lsb-4.0.repo:

name=LSB 4

For zypper, again you create an LSB repo file like /etc/zypp/repos.d/lsb-ia32.repo:


Then the package installation would look something like:

apt-get install lsb-appchk lsb-pkgchk lsb-build-cc lsb-build-c++


yum install lsb-appchk lsb-pkgchk lsb-build-cc lsb-build-c++


zypper in lsb-appchk lsb-pkgchk lsb-build-cc lsb-build-c++

You'll note we omitted lsb-setup and lsb-build-base. This is because the package manager now resolves the dependencies and pulls these packages in with the others.

Building and verifying an RPM is beyond the scope of the tutorial. Instead, let's focus on building a small C application with lsbcc and scanning the resulting binary for invalid symbols with lsb-appchk.

An Example Program

Listing 1 shows a small program that echoes its command-line arguments (error-checking code has been omitted intentionally).

Listing 1. A Simple C Program

#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>

main(argc, argv)
int argc;
char *argv[];
  int i = 0;

  for (i = 1; i < argc; i++) {
   fputs(argv[i], stdout);
   putchar(' ');

Copy and paste the code into a file named echoargs.c, and then build it with the compiler installed on your Debian system:

$ cc -o echoargs echoargs.c 
$ ./echoargs hello there, world!
hello there, world!

The code works as intended, but is it LSB conforming? To make the determination, run the lsbappchk command:

$ /opt/lsb/bin/lsbappchk echoargs
LSB version is not specified, using 4.0 by default.

BIN: echoargs
LSB Application Checker Report

Binary echoargs:
  Incorrect program interpreter: /lib/

Section .interp not checked
Section .note.ABI-tag not checked
section .gnu.hash is not in the LSB
  section .gnu.hash is not in the LSB

Echoargs is clearly not an LSB-conforming application.

**Use the LSB Compiler to Make the Application Conform**

Now, rebuild the same code using the LSB compiler–lsbcc–and run lsbappchk on the binary it produces:

$ /opt/lsb/bin/lsbcc -o lsb-echoargs echoargs.c
$ /opt/lsb/bin/lsbappchk lsb-echoargs
LSB version is not specified, using 4.0 by default.

BIN: lsb-echoargs
LSB Application Checker Report

(there is additional output, but no FAIL messages)

Much better! The new binary is conforming. It was built with the LSB stub libraries using the LSB include files (header files) instead of the system header files. But does the application run?

$ ./lsb-echoargs foo bar
$ foo bar

While not yet certified, Ubuntu Hardy is indeed lsb conforming. If running the application gave this type of message:

$ ./lsb-echoargs foo bar
-bash: no such file or directory: ./lsb-echoargs

It would be an indication that the system is not LSB V4.0 conformant, so the binary cannot be executed. The command ./lsb-echoargs produces the somewhat odd message, -bash: ./lsb-echoargs: No such file or directory, which belies the real error–namely, that the system cannot load the binary. (In a moment, you'll use the LSB Sample Implementation to run this binary.)

As another example, consider Listing 2. The code snippet uses the open source Perl Compatible Regular Expressions (PCRE) library to add the power of regular expressions to traditional C. As useful as PCRE is, it's not part of the LSB specification.

On Ubuntu Hardy, you need to install libpcre3-dev to build this example. On other systems the package name may be different

$ apt-get install libpcre3-dev**\\ **

Listing 2. A Snippet of a PCRE Application

#include <pcre.h>

int main()
  pcre *re;
  const char *error;
  int erroffset;

  /* more code here */
  re = pcre_compile("^[A-Z]", 0, &error, &erroffset, NULL);

  /* rest of the application */

You can build the code with the command cc -o pcre pcre.c -lpcre.. Checking the code with lsbappchk produces additional error messages:

$ cc -o pcre pcre.c -lpcre
$ /opt/lsb/bin/lsbappchk pcre

LSB version is not specified, using 4.0 by default.

BIN: pcre
LSB Application Checker Report

Binary pcre:
  Incorrect program interpreter: /lib/
  DT_NEEDED: is used, but not part of the LSB
  Symbol pcre_compile is used, but is not included in LSB 4.0 (Core & C++ & Desktop)

The functions declared by PCRE are not LSB compliant and are flagged. You could avoid this error (assuming that the rest of the PCRE library was LSB compliant) by adding the -static flag when compiling.

Interestingly, the same command using lsbcc does not generate errors:

$ /opt/lsb/binlsbcc -o lsb-pcre pcre.c -lpcre
$ /opt/lsb/bin/lsbappchk lsb-pcre
LSB version is not specified, using 4.0 by default.

BIN: lsb-pcre
LSB Application Checker Report

Again, a lot of output, but no FAIL messages. Let's look at the symbols in lsb-pcre:

$ nm lsb-pcre | grep pcre
08051be0 R _pcre_OP_lengths
08058240 R _pcre_default_tables
0804fd40 T _pcre_is_newline
08050020 T _pcre_ord2utf8
08050090 T _pcre_ucp_findprop
08050130 T _pcre_ucp_othercase
08051c50 R _pcre_utf8_table1
08051c68 R _pcre_utf8_table1_size
08051c6c R _pcre_utf8_table2
08051c84 R _pcre_utf8_table3
08051ca0 R _pcre_utf8_table4
08051f80 R _pcre_utt
08051ce0 R _pcre_utt_names
080521f8 R _pcre_utt_size
080501b0 T _pcre_valid_utf8
0804fec0 T _pcre_was_newline
080597c8 B pcre_callout
0804fd00 T pcre_compile
0804f340 T pcre_compile2
080597b8 D pcre_free
080597b4 D pcre_malloc
080597c0 D pcre_stack_free
080597bc D pcre_stack_malloc

Here, lsbcc statically linked the PCRE code into the executable – one solution to avoid library differences between one Linux platform and another. Lsbcc modifies command-line arguments to the GCC compiler to use LSB header files and libraries and to avoid dynamic links to non-compliant LSB libraries.

If you use GCC and a number of home-grown or popular tools to build your code, lsbcc is probably preferable over the chroot LSB Build Environment. In contrast, if you use a compiler other than GCC or have dependencies on a specific compiler, compiler options, or library or include file paths, the LSB Build Environment may be superior. The next section demonstrates how to install and use the LSB Sample Implementation to test your application. Both the Build Environment and the Sample Implementation have been redesigned for LSB V4.0. As of this writing the Build Environment is not yet ready for testing. When available, it will be similar to the Sample Implementation, a standalone minimal system. Basically the Sample Implementation with the addition of the SDK.

**Installing the Sample Implementation**

Note: The rest of this tutorial uses the virtual lsb-siX-vm instance of openSUSE 11.1 running in VMWare Workstation. If you previously suspended the VM or quit VMWare Workstation, resume the VM or re-launch VMWare Workstation and start the lsb-siX-vm instance. When the instance is running, you should be logged in as tux automatically.

**Download and Install the chroot LSB Sample Implementation**

This section only applies if you are using a different OS or virtual machine than the lsb-siX-vm. The LSB appliance already has lsbsi-chroot and lsbsi-tools installed. If you are using the lsb-siX-vm, please skip ahead to the section on using the SI.

The Sample Implementation is distributed as the lsbsi-choot rpm package, with a supporting lsbsi-tools package which helps integrate the SI as a “application” on the host system. Because of the complexity of the SI, it tends to lag the full LSB release slightly, and at the time of this writing it is still in beta. For what we're doing in this demo, the beta release should be sufficient.

1 $ wget
2 $ wget

3 $ rpm -ivh lsbsi-chroot-4.0.1-1.i586.rpm lsbsi-tools-4.0.0-1.i586.rpm

Commands 1-2 download the pieces of the LSB Sample Implementation. Command 3 installs them on the system.

  • lsbsi-chroot is the core of the Sample Implementation. It installs in opt/lsb/si/chroot.
  • lsbsi-tools is a set of scripts and menu entry that facilitate your chroot into the SI system. The scripts provide the proper bind mounts and environment that enable the SI chroot to behave much like a “real” system. An lsbsi group is added to the system at package install. By adding users to this group, non-root users will also be able to use the SI.

After you install the Sample Implementation, you can use chroot to get to it. You can either run the command /opt/lsb/bin/si-chroot, the command /opt/lsb/si/tools/si, the command /opt/lsb/si/tools/si-gui, or select the menu entry Development|LSB Sample Implementation. To exit the chroot environment, press Ctrl+D at the new shell prompt.

**Executing Code in the Sample Implementation**

Build the simple code of Listing 1 within openSUSE 11.1 and run it within the Sample Implementation.

**Install the SDK**

To make things convenient for development, the lsb-siX-vm openSUSE 11.1 environment provides gcc and LSB SDK. If you are using another system, you would need the install a compiler and the LSB build tools as outlined earlier.

Within your openSUSE 11.1 VM, you now have two environments: the openSUSE environment, with the SDK, and the Sample Implementation. There should be a terminal window open already within the Sample Implementation and if you open another tab or window, you should be the “tux” user in that home directory. For convenience, tux's home directory is bind mounted under /root/myfiles within the SI:

tux user:

$ pwd
$ /home/tux
$ touch foo

root user in the SI:

$ cd /root/myfiles
$ ls -1

So, to build Listing 1 with the SDK and test it in the chroot Sample Implementation, you download the code to the openSUSE 11.1 environment, and then build it per the following sequence (the prefixes in the command-line prompt were added for clarity):

(tux) $ wget (tux) $ /opt/lsb/bin/lsbcc -o echoargs echoargs.c (si) $ cd /root/myfiles (si) $ ./echoargs hello there hello there

By the way, because openSUSE 11.1 is nearly compliant with LSB V4.0.0, the binary you created with lsbcc runs fine in the openSUSE:

(tux) $ ./echoargs this is cool
this is cool**\\ **


While the example code shown in this tutorial was simple, the same techniques used to build and test a few lines of code apply equally well to a few thousand lines of code. Use the lsb-appchk tool to find questionable symbols. Try building your code with the LSB Build Environment utilities and within the stand-alone LSB Build Environment chroot environment. If you don't have an LSB V4.0.0-compliant version of Linux, use the LSB Sample Implementation to test the portability of your application. Leverage a tool such as VMWare Workstation to virtually (both metaphorically and practically) multiply your computing resources and run your targeted flavors of Linux.

With a little work, you can shape your application to be LSB compliant, and then apply to have your application certified. Certified distributions and certified applications allow users to invest in Linux comfortably. The LSB provides uniformity, which–perhaps paradoxically–promotes choice.

And after all, choice is what Linux is all about.


This article originally appeared on IBM developerWorks. It has been revised to current technology practices. Thanks to Ted T'So and Jeff Licquia for updating it. The current version has been updated to reflect changes with LSB V4.0.

lsb/porting-lsb-demo.txt · Last modified: 2016/07/19 01:23 (external edit)