lorder(1)                                               lorder(1)



     NAME
          lorder - find ordering relation for an object library

     SYNOPSIS
          lorder file ...

     DESCRIPTION
          lorder produces a global cross-reference, given a list of
          object modules (.o files), which can then be passed to
          tsort(1) to produce a properly ordered archive file.  The
          input is one or more object or library archive files (see
          ar(1)).  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.  The output may
          be processed by tsort(1) to find an ordering of a library
          suitable for one-pass access by ld(1).  The link editor
          ld(1) is capable of multiple passes over an archive in the
          portable archive format (see ar(4)) and does not require
          that lorder(1) be used when building an archive.

          Use of the lorder(1) command may, however, allow for a
          slightly more efficient access of the archive during the
          link edit process.

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

          builds a new library from existing .o files.

     FILES
          /bin/lorder
temporary *symref, *symdef

     SEE ALSO
          ar(1), ld(1), tsort(1), ar(4),
          ``Other tools'' in Oreo Programming Languages and Tools,
          Volume 2.

     BUGS
          Object files whose names do not end with .o, even when
          contained in library archives, are overlooked.  Their global
          symbols and references are attributed to some other file.













     Page 1                                        (last mod. 1/16/87)