Go to main content

man pages section 1: User Commands

Exit Print View

Updated: Thursday, March 14, 2019
 
 

lorder(1)

Name

lorder - find ordering relation for an object or library archive

Synopsis

lorder filename...

Description

The input is one or more object or library archive filenames (see ar(1)). The standard output is a list of pairs of object file or archive member names; the first file of the pair refers to external identifiers defined in the second. The output may be processed by tsort(1) to find an ordering of a library suitable for one-pass access by ld. Note that the link editor ld is capable of multiple passes over an archive in the portable archive format (see ar.h(3HEAD)) and does not require that lorder be used when building an archive. The usage of the lorder command may, however, allow for a more efficient access of the archive during the link edit process.

The following example builds a new library from existing .o files.

ar –cr  library  ` lorder  *.o  |  tsort `

Files

TMPDIR/*symref

temporary files

TMPDIR/*symdef

temporary files

TMPDIR

usually /var/tmp but can be redefined by setting the environment variable TMPDIR. See tempnam() in tmpnam(3C)).

Attributes

See attributes(7) for descriptions of the following attributes:

ATTRIBUTE TYPE
ATTRIBUTE VALUE
Availability
developer/base-developer-utilities

See Also

ar(1), ld(1), tsort(1), tmpnam(3C), ar.h(3HEAD), attributes(7)

Notes

lorder will accept as input any object or archive file, regardless of its suffix, provided there is more than one input file. If there is but a single input file, its suffix must be .o.

The length of the filename for TMPDIR is limited to whatever sed allows.