NAME

lorder − find ordering relation for an object library

SYNOPSIS

lorder file ... 

DESCRIPTION

The input is one or more object or library archive files (see ar(1)).  The standard output is a list of pairs of object file names, meaning that 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(1).  Note that the link editor ld(1) is capable of multiple passes over an archive in the portable archive format (see ar(4)) and does not require that lorder(1) be used when building an archive.  The usage of the lorder(1) command may, however, allow for a slightly 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

∗symref, ∗symdeftemporary files

SEE ALSO

ar(1), ld(1), tsort(1). 
ar(4) in the CX/UX Programmer’s Reference Manual. 

BUGS

Object files whose names do not end with .o, even when contained in library archives, are overlooked.  Their global symbols and references are attributed to some other file. 

CX/UX User’s Reference Manual