| 1 | .\" Copyright (c) 1980 Regents of the University of California. |
| 2 | .\" All rights reserved. The Berkeley software License Agreement |
| 3 | .\" specifies the terms and conditions for redistribution. |
| 4 | .\" |
| 5 | .\" @(#)lorder.1 6.1 (Berkeley) %G% |
| 6 | .\" |
| 7 | .TH LORDER 1 "" |
| 8 | .UC 4 |
| 9 | .SH NAME |
| 10 | lorder \- find ordering relation for an object library |
| 11 | .SH SYNOPSIS |
| 12 | .B lorder |
| 13 | file ... |
| 14 | .SH DESCRIPTION |
| 15 | The input |
| 16 | is one or more object or library archive (see |
| 17 | .IR ar (1)) |
| 18 | .I files. |
| 19 | The standard output |
| 20 | is a list of pairs of object file names, |
| 21 | meaning that the first file of the pair refers to |
| 22 | external identifiers defined in the second. |
| 23 | The output may be processed by |
| 24 | .IR tsort (1) |
| 25 | to find an ordering of |
| 26 | a library suitable for one-pass access by |
| 27 | .IR ld (1). |
| 28 | .PP |
| 29 | This brash one-liner intends to build a new library |
| 30 | from existing `.o' files. |
| 31 | .IP |
| 32 | ar cr library \`\|lorder *.o | tsort\` |
| 33 | .PP |
| 34 | The need for lorder may be vitiated by use of |
| 35 | .IR ranlib (1), |
| 36 | which converts an ordered archive into a randomly |
| 37 | accessed library. |
| 38 | .SH FILES |
| 39 | *symref, *symdef |
| 40 | .br |
| 41 | nm(1), sed(1), sort(1), join(1) |
| 42 | .SH "SEE ALSO" |
| 43 | tsort(1), |
| 44 | ld(1), |
| 45 | ar(1), |
| 46 | ranlib(1) |
| 47 | .SH BUGS |
| 48 | The names of object files, in and out of libraries, must end with `.o'; |
| 49 | nonsense results otherwise. |