Use of lorder(1) is not required by contemporary linkers.
The GNU coreutils manual[1] has a good description of the use of lorder
and tsort:
This whole procedure has been obsolete since about 1980, because
Unix archives now contain a symbol table (traditionally built by
ranlib, now generally built by ar itself), and the Unix linker uses
the symbol table to effectively make multiple passes over an archive
file.
See 0e1e341b48
for some more details.
[1] https://www.gnu.org/software/coreutils/manual/html_node/tsort-background.html
PR: 259254 [exp-run]
MFC after: 2 weeks
Sponsored by: The FreeBSD Foundation
98 lines
2.8 KiB
Groff
98 lines
2.8 KiB
Groff
.\" Copyright (c) 1990, 1993
|
|
.\" The Regents of the University of California. All rights reserved.
|
|
.\"
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
.\" modification, are permitted provided that the following conditions
|
|
.\" are met:
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
.\" 3. Neither the name of the University nor the names of its contributors
|
|
.\" may be used to endorse or promote products derived from this software
|
|
.\" without specific prior written permission.
|
|
.\"
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
.\" SUCH DAMAGE.
|
|
.\"
|
|
.\" @(#)lorder.1 8.2 (Berkeley) 4/28/95
|
|
.\" $FreeBSD$
|
|
.\"
|
|
.Dd December 20, 2021
|
|
.Dt LORDER 1
|
|
.Os
|
|
.Sh NAME
|
|
.Nm lorder
|
|
.Nd list dependencies for object files
|
|
.Sh SYNOPSIS
|
|
.Nm
|
|
.Ar
|
|
.Sh DESCRIPTION
|
|
The
|
|
.Nm
|
|
utility uses
|
|
.Xr nm 1
|
|
to determine interdependencies in the list of object files
|
|
and library archives
|
|
specified on the command line.
|
|
The
|
|
.Nm
|
|
utility outputs a list of file names where the first file contains a symbol
|
|
which is defined by the second file.
|
|
.Pp
|
|
The output is normally used with
|
|
.Xr tsort 1
|
|
when a library 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.
|
|
.Pp
|
|
When linking static binaries,
|
|
.Nm
|
|
and
|
|
.Xr tsort 1
|
|
can be used to properly order library archives automatically.
|
|
.Pp
|
|
The use of
|
|
.Nm
|
|
is not required by contemporary linkers, and
|
|
.Nm
|
|
may be removed from a future version of
|
|
.Fx .
|
|
.Sh ENVIRONMENT
|
|
.Bl -tag -width indent
|
|
.It Ev NM
|
|
Path to the
|
|
.Xr nm 1
|
|
binary, defaults to
|
|
.Dq Li nm .
|
|
.It Ev NMFLAGS
|
|
Flags to pass to
|
|
.Xr nm 1 .
|
|
.El
|
|
.Sh EXAMPLES
|
|
.Bd -literal -offset indent
|
|
ar cr library.a `lorder ${OBJS} | tsort`
|
|
cc -o foo ${OBJS} `lorder ${STATIC_LIBS} | tsort`
|
|
.Ed
|
|
.Sh SEE ALSO
|
|
.Xr ar 1 ,
|
|
.Xr ld 1 ,
|
|
.Xr nm 1 ,
|
|
.Xr ranlib 1 ,
|
|
.Xr tsort 1
|
|
.Sh HISTORY
|
|
A
|
|
.Nm
|
|
utility appeared in
|
|
.At v7 .
|