Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!ctrsol!ginosko!uunet!ssbell!kent From: kent@ssbell.UUCP (Kent Landfield) Newsgroups: comp.unix.xenix Subject: Re: rkive under SCO 386 Message-ID: <533@ssbell.UUCP> Date: 29 Jul 89 16:51:34 GMT References: <379@ubbs-nh.MV.COM> Reply-To: kent@ssbell.UUCP (ssbell Admin) Organization: Sterling Software, FSG-IMD, Bellevue, NE. Lines: 37 In article <379@ubbs-nh.MV.COM> noel@ubbs-nh.MV.COM (Noel B. Del More Nashua) writes: >I am experiancing a problem at this moment in time, ie. a compile >failure reporting the lack of /usr/include/dirent.h > >I would truely appreciate hearing from anyone who has this program >compiled and operating under SCO Xenix 386 2.3.1. > It is my fault that I caused people extra work here. I am sorry that I didn't make it clear in the README about the directory access routines and my feelings on the subject but I am a RPDCM (Rabid POSIX Directory Compliant Maniac). :-) I do not want to make the code ugly with ifdefs for the ndir.h, dir.h sys/dir.h etc. Since *all* the major vendors *say* they are becoming POSIX compliant in their next release (whenever that is) I felt that I should help them along and keep my code as clean as possible. :-) If you do not have access to Doug Gwyn's Directory library which was posted to c.s.u a while back, get them. These are extremely useful whether you are using rkive or not. In the mean time, one quick way to get around the directory stuff (if you don't want to use the POSIX directory routines) is to create a new include file "/usr/include/dirent.h" that contains something like the following: /* /usr/include/dirent.h */ #include #define dirent direct Otherwise you could go through all the source files and change dirent.h to ndir.h and all struct dirent to struct direct... Naaah. :-) :-) -Kent+ -- Kent Landfield UUCP: kent@ssbell Sterling Software FSG/IMD INTERNET: kent@ssbell.uu.net 1404 Ft. Crook Rd. South Phone: (402) 291-8300 Bellevue, NE. 68005-2969 FAX: (402) 291-4362