[comp.sys.att] Gyyn's directory stuff on UnixPC

wouk@romeo.cs.duke.edu (Arthur Wouk) (04/25/89)

i am looking into putting Doug Gwyn's port of bsd-like directory
routines to my 3b1. i find two sets of sources: one very small called
libndir and a much larger one called libndir-posix, both at simtel20.
as i study the installation i deduce that i want to put the  object
code in /lib/libc.a. where, however. Gwyn suggests a place which i
can't locate. in addition, how can one choose between the two versions?
i ask the following questions of anyone who has installed this code:

does either of them present a problem on the 3b1 under 3.51?

where in libc.a did you put the files?

sadler@heurikon.UUCP (Jon Sadler) (04/25/89)

In article <14290@duke.cs.duke.edu> wouk@romeo.cs.duke.edu (Arthur Wouk) writes:
>i am looking into putting Doug Gwyn's port of bsd-like directory
>routines to my 3b1. i find two sets of sources: one very small called
>libndir and a much larger one called libndir-posix, both at simtel20.
[deleted lines]
>i ask the following questions of anyone who has installed this code:
>
>does either of them present a problem on the 3b1 under 3.51?
>
>where in libc.a did you put the files?

In a former life, I worked on about 110 3b1's at a major university.  One of
the first things I "brought up" were the ndir routines.  These were retrieved
from j.cc.purdue.edu, home of the (internet) archive site for comp.sources.unix.
I am not sure which package corresponds to (whether libndir or libndir-posix)
but it was not hard to get the package up and running on the 3b1.
Basically, all that I did was place the appropriate dirent.h files into
/usr/include and /usr/include/sys, and then compile the source.  The
resulting .o files are run through ranlib.  (We didn't have ranlib on the
3b1, so I just skipped this step.)  Next, I used ar to "tack" the .o files
onto /lib/libc.a.  They ended up on the END of the archive file, but this
should not matter since there are not any other funcations in libc.a that
have the same name as the routines in ndir.

Since then, I have not run into any problems with the instalation of
these routines.  (This numbers over 100 computer-years of use.)

If you have any questions, or problems, feel free to get in contact with me.

Jonathan Sadler
Heurikon Corp.

-- 
BANG PATH:      ...rutgers!uwvax!heurikon!sadler   SNAIL: Jonathan Sadler
                ...rutgers!nucsrl!laidbak!sadler          Heurikon Corp.
UUCP DOMAIN:    sadler@heurikon.UUCP                      3201 Latham Drive
                sadler@laidbak.UUCP                       Madison, WI 53713
ARPA:           sadler@csd4.milw.wisc.edu          PHONE: (608) 271-8700

lenny@icus.islp.ny.us (Lenny Tropiano) (04/28/89)

In article <326@heurikon.UUCP> sadler@heurikon.UUCP (Jon Sadler) writes:
...
|>/usr/include and /usr/include/sys, and then compile the source.  The
|>resulting .o files are run through ranlib.  (We didn't have ranlib on the
|>3b1, so I just skipped this step.)  Next, I used ar to "tack" the .o files
...

Instead of "ranlib" use this:

ar rv libdirent.a `lorder *.o | tsort`

							-Lenny
-- 
Lenny Tropiano             ICUS Software Systems         [w] +1 (516) 582-5525
lenny@icus.islp.ny.us      Telex; 154232428 ICUS         [h] +1 (516) 968-8576
{talcott,decuac,boulder,hombre,pacbell,sbcs}!icus!lenny  attmail!icus!lenny
        ICUS Software Systems -- PO Box 1; Islip Terrace, NY  11752

guy@auspex.auspex.com (Guy Harris) (05/03/89)

 >|>/usr/include and /usr/include/sys, and then compile the source.  The
 >|>resulting .o files are run through ranlib.  (We didn't have ranlib on the
 >|>3b1, so I just skipped this step.)  Next, I used ar to "tack" the .o files
 >...
 >
 >Instead of "ranlib" use this:

Does not the UNIX PC have an S5-style "ar"?  Does not that flavor of "ar"
have "ranlib" built into it, so that the "table of contents" gets
rebuilt whenever you update the archive?  (It certainly did as of S5R2,
but that doesn't necessarily mean the UNIX PC has it - S5R2 had a
4.xBSD-derived archive format, but S5"R1" had a different format, so
maybe the table-of-contents stuff appeared later; I don't think it did,
but I no longer have S5"R1" source handy to check.)