Xref: utzoo comp.protocols.tcp-ip.ibmpc:4201 comp.protocols.nfs:1520
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!tmc.edu!sob
From: sob@tmc.edu (Stan Barber)
Newsgroups: comp.protocols.tcp-ip.ibmpc,comp.protocols.nfs
Subject: PC-NFS toolkit and Microsoft C
Message-ID: <2743@gazette.bcm.tmc.edu>
Date: 14 Nov 90 00:16:33 GMT
Sender: usenet@bcm.tmc.edu
Followup-To: comp.protocols.tcp-ip.ibmpc
Organization: Baylor College of Medicine, Houston, Tx
Lines: 30
Nntp-Posting-Host: tmc.edu
Originator: sob@tmc.edu

Sun Bug ID 1007134 discusses the problems of using PC-NFS toolkit with 
Microsoft C 5.0 (and 5.1). The problem is due to the fact that PC-NFS
toolkit include files and the Microsoft C include files both define
size_t.

Sun suggests that the toolkit include files be listed first in the
include environmental variable.

For example, if the toolkit includes are in c:\toolkit\include and the
Microsoft C include files are in d:\include, then execute this command to
set the include environmental variable up to workaround the problem:

set include=c:\toolkit\include;d:\include

What I did was to alter the stuff in the toolkit include file sys\types.h
to have the same type of format as the stuff in the microsoft C include
file of the same name.

#ifdef _INO_T_DEFINED
typedef unsigned short ino_t;
#define _INO_T_DEFINED
#endif

etc.


-- 
Stan           internet: sob@bcm.tmc.edu         Director, Networking 
Olan           uucp: {rutgers,mailrus}!bcm!sob   and Systems Support
Barber         Opinions expressed are only mine. Baylor College of Medicine