LORDER(1) UNIX Programmer's Manual LORDER(1)
lorder - find ordering relation for an object library
S
\bSY
\bYN
\bNO
\bOP
\bPS
\bSI
\bIS
\bS
l
\blo
\bor
\brd
\bde
\ber
\br file ...
D
\bDE
\bES
\bSC
\bCR
\bRI
\bIP
\bPT
\bTI
\bIO
\bON
\bN
The input is one or more object or library archive (see
_
\ba_
\br(1)) _
\bf_
\bi_
\bl_
\be_
\bs. 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 _
\bt_
\bs_
\bo_
\br_
\bt(1) to find an ordering of a
library suitable for one-pass access by _
\bl_
\bd(1).
This brash one-liner intends to build a new library from
ar cr library `lorder *.o | tsort`
The need for lorder may be vitiated by use of _
\br_
\ba_
\bn_
\bl_
\bi_
\bb(1),
which converts an ordered archive into a randomly accessed
nm(1), sed(1), sort(1), join(1)
S
\bSE
\bEE
\bE A
\bAL
\bLS
\bSO
\bO
tsort(1), ld(1), ar(1), ranlib(1)
The names of object files, in and out of libraries, must end
with `.o'; nonsense results otherwise.
Printed 7/9/88 April 29, 1985 1
projects / unix-history / blob