xref: /original-bsd/usr.bin/lorder/lorder.1 (revision dbe44373)
Copyright (c) 1990 The Regents of the University of California.
All rights reserved.

Redistribution and use in source and binary forms are permitted
provided that the above copyright notice and this paragraph are
duplicated in all such forms and that any documentation,
advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed
by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

@(#)lorder.1 6.2 (Berkeley) 03/20/90

LORDER 1 ""
C 4
NAME
lorder - list dependencies for object files
SYNOPSIS
lorder file ...
DESCRIPTION
The lorder utility uses nm (1) to determine interdependencies in the list of object files specified on the command line. Lorder outputs a list of file names where the first file contains a symbol which is defined by the second file.

The output is normally used with tsort (1) when a libarary is created to determine the optimum ordering of the object modules so that all references may be resolved in a single pass of the loader.

EXAMPLES

ar cr library.a `lorder ${OBJS} | tsort`

"SEE ALSO"
ar(1), ld(1), nm(1), ranlib(1), tsort(1)