lorder(1)                  DG/UX 4.30                   lorder(1)



     NAME
          lorder - find ordering relation for an object library

     SYNOPSIS
          lorder file ...

     DESCRIPTION
          Lorder reads each object or archive file and produces a list
          of pairs of object file or archive member names.  The first
          file of each pair refers to external identifiers defined in
          the second file.

          The output may be processed by tsort(1) to find an ordering
          of a library suitable for one-pass access by ld(1).  Note
          that the link editor ld(1) can perform 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.  Using lorder(1) may, however, allow for a slightly
          more efficient access of the archive during the link edit
          process.

          The following example builds a new library from existing
          object files:

               ar cr library `lorder *.o | tsort`

     FILES
          TMPDIR/*symref
                        Temporary file of symbol references

          TMPDIR/*symdef
                        Temporary file of symbol definitions

          TMPDIR        TMPDIR is usually /usr/tmp but can be
                        redefined by setting the environment variable
                        TMPDIR [see tmpnam()] in tmpnam(3s)].

     SEE ALSO
          ar(1), ld(1), tsort(1), ar(4).

     CAVEAT
          lorder will accept as input any object or archive file,
          regardless of its suffix, provided there is more than one
          input file.  If there is but a single input file, its suffix
          must be .o.










     Licensed material--property of copyright holder(s)         Page 1