User Commands lorder(1)
NAME
lorder - find ordering relation for an object or library
archiveSYNOPSIS
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 orderingof 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)) anddoes 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(5) for descriptions of the following attri-
butes:SunOS 5.11 Last change: 29 Oct 1991 1
User Commands lorder(1)
____________________________________________________________
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|_____________________________|_____________________________|
| Availability | developer/object-file |
|_____________________________|_____________________________|
SEE ALSO
ar(1), ld(1), tsort(1), tmpnam(3C), ar.h(3HEAD), attri-
butes(5) NOTESlorder 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.SunOS 5.11 Last change: 29 Oct 1991 2