Museum

Home

Lab Overview

Retrotechnology Articles

⇒ Online Manual

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

ar(1)

join(1)

ld(1)

nm(1)

sed(1)

sort(1)

tsort(1)

LORDER(1)                            BSD                             LORDER(1)



NAME
     lorder - find ordering relation for an object library

SYNOPSIS
     lorder file ...

DESCRIPTION
     The input is one or more object or library archive (see ar(1)) files. The
     standard output is a list of pairs of object filenames, meaning that the
     first file of the pair refers to external identifiers defined in the
     second.  You can use tsort(1) to process the output, to find an ordering
     of a library suitable for one-pass access by ld(1).

EXAMPLE
     This brash one-liner intends to build a new library from existing .o
     files.

          % ar cr library `lorder *.o | tsort`


NOTE
     The need for lorder has vanished on Domain/OS systems, since ar(1) and
     ld(1) cooperate to create randomly accessed libraries.

FILES
     *symref
     *symdef

BUGS
     The names of object files, in and out of libraries, must end with .o;
     nonsense results otherwise.

SEE ALSO
     ar(1), join(1), ld(1), nm(1), sed(1), sort(1), tsort(1)

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026