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