Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ lorder(1) — svr4 — mips UMIPS RISC/os 5.01

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

ar(1)

ld(1)

tsort(1)

ar(4)



LORDER(1-SVR4)      RISC/os Reference Manual       LORDER(1-SVR4)



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 or archive member 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 multi-
     ple 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
     TMPDIR/*symref temporary files

     TMPDIR/*symdef temporary files

     TMPDIR is usually /usr/tmp but can be redefined by setting
     the environment variable TMPDIR [see tempnam() in
     tmpnam(3S)].

SEE ALSO
     ar(1), ld(1), tsort(1), ar(4).

CAVEAT
     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.













                        Printed 11/19/92                   Page 1



Typewritten Software • bear@typewritten.org • Edmonds, WA 98026