Tips-n-tricks

There is a way to get a full list of all options available for the Compiler, Assembler and Linker and save it for future reference. There are two options that are used. These options are -v and –help. For example to get the options using gcc do the following: gcc -v –help > compile-options.txt 2>&1 This will create the list in the file compile-options.txt. Any editor can then be used to look at the file.

If you are using qmake as build tool, all you need to do is to make sure that /opt/lsb/bin comes first in your PATH environment variable. Simply re-run qmake and make to produce LSB compliant binaries:

export PATH=/opt/lsb/bin:$PATH
qmake
make

If, for some reason, you don't want to use LSB's qmake, make sure to set the environment variable QMAKESPEC to linux-lsb before running qmake:

export QMAKESPEC=linux-lsb
qmake
make

The linux-lsb qmake spec was added in Qt 4.1.

This section describes how to migrate the applications base on Gtk+-2.0 to make it LSB compliant. There are many depricated, experimenatal and private functions exposed by GTK which are not meant for application developers and hence are not in LSB 3.1. Fortunately, Gtk maintainers have written some documents explaining how to move from some of the depricated set of interefaces to new ones.

The LSB specifies inet_ntop and inet_pton for address conversion, since these are both IPv4 and IPv6 capable. You can start using these functions by replacing calls of the form

foo.sin_addr.s_addr = inet_addr(cp);

with

inet_pton(AF_INET, cp, &foo.sin_addr);

calls of the form

inet_aton(cp, &foo.sin_addr);

with

inet_pton(AF_INET, cp, &foo.sin_addr);

and calls of the form

ptr = inet_ntoa(foo.sin_addr);

with

partial obstack support appeared in earlier versions of the LSB but the implementation was never complete. The partial bits were removed in the LSB 2.x timeframe. One comment at the time was: Obstacks are a memory management library built on top of malloc. As far as I know applications generally (always?) have their own copy of the obstack code, and don't have any particular need to use the glibc one. The complexity of obstacks are pretty horrendous considering the functionality is pretty simple.