lsbappchk(1)

NAME

lsbappchk - check LSB conformance of application

SYNOPSIS

lsbappchk  [-o  outputfile]  [-A]  [-M   modulename]   [-L
pathtolib]...  appname...

DESCRIPTION

Measure an application executable's conformance to the

Linux Standard Base (LSB) specification. The object format of the

application is checked, as is the list of shared libraries used

by the application, and the list of functions and global data

used by the application. Warnings are produced for anything that

is referenced but not contained in the LSB specification. lsbap

pchk's view of valid libraries and interfaces can be expanded.

-o outputfile

Write the journal file (see below) to outputfile

instead of to the default filename in the current directory.

-A Check the symbols found in all modules.

-M modulename

Check only the symbols found in module modulename.

-L nameoflib

Specify the full pathname of a shared library which

is part of the application. This option can be specified as many

times as needed, and will prevent lsbappchk from complaining

about symbols which are provided in those shared libraries. The

order of libraries specified this way is significant: since ls

bappchk does not actually run the application, it cannot deduce

the library dependency graph.

A journal file is created named journal.appchk.appname,

where appname is the first binary specified. It contains a record

of the test results in a format that can be submitted for LSB

Certification. You must have write access to the current working

directory in order to run lsbappchk successfully, or use the -o

option to specify an alternate location for the journal.

The lsbappchk program cannot detect all conformance prob

lems. In particular, it is a static test and does not actually

run the application. Lsbappchk will not find any behaviors which

show themselves only at run-time (for example, anything involving

the File Hierarchy Standard, or constants and other such items

which are found in header files). Lsbappchk will warn that it

cannot determine the validity of a call to ioctl. The dynamic

checker should be used to test run-time behavior.

NOTES

lsbappchk is intended to be used on applications compiled

in LSB mode. When used as an analysis tool on native applica

tions, it will likely report failures, such as symbols with the

wrong symbol version, which will vanish when the application is

compiled correctly.

AUTHORS

The contributors to the Linux Standard Base.

REPORTING BUGS

Report bugs to <lsb-test@linuxbase.org>.

SEE ALSO

Linux Standard Base specification and other documents at

http://www.linuxbase.org/

lsbappchk (LSB)

lsbappchk(1)