


      LLLLOOOORRRRDDDDEEEERRRR((((1111))))                   ((((bbbbssssdddd 4444....2222))))                   LLLLOOOORRRRDDDDEEEERRRR((((1111))))



      NNNNAAAAMMMMEEEE
           lorder - find ordering relation for an object library

      SSSSYYYYNNNNTTTTAAAAXXXX
           lllloooorrrrddddeeeerrrr file ...

      DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
           The input is one or more object or library archive (see
           _a_r(1)) _f_i_l_e_s. The standard output is a list of pairs of
           object file names, meaning that the first file of the pair
           refers to external identifiers defined in the second.  The
           output may be processed by _t_s_o_r_t(1) to find an ordering of a
           library suitable for one-pass access by _l_d(1).

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

                ar cr library `lorder *.o | tsort`

           The need for lorder may be vitiated by use of _r_a_n_l_i_b(1),
           which converts an ordered archive into a randomly accessed
           library.

      FFFFIIIILLLLEEEESSSS
           *symref, *symdef
           nm(1), sed(1), sort(1), join(1)

      SSSSEEEEEEEE AAAALLLLSSSSOOOO
           tsort(1), ld(1), ar(1), ranlib(1)

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






















      Page 1                                                   (9010-E)



