Path: utzoo!attcan!uunet!samsung!uakari.primate.wisc.edu!uflorida!mephisto!udel!garrett@oscar.ccm.udel.edu
From: garrett@oscar.ccm.udel.edu
Newsgroups: comp.protocols.tcp-ip
Subject: Problems with WIN/TCP v5.1...
Message-ID: <25049@nigel.udel.EDU>
Date: 19 Jul 90 13:32:48 GMT
Sender: usenet@ee.udel.EDU
Organization: Univ. of Delaware, CCM
Lines: 80

Greetings, all...  We have just had the latest version of WIN/TCP (v5.1)
installed here at our site and I finally decided to sit down and learn how to
use the library/system call interface for VAXC...

Before I get into the details, we have the software installed on a 785 running
VMS v4.7 and VAXC v2.4

I have been following the examples in the WIN/TCP Programming Guide...

I found example source code in the directory TWG$TCP:[NETDIST.TUTORIAL.EXAMPLE]
(SERV.C, and CLIENT.C)

When I tried compiling these programs, I found that evidently some #include
files appeared to be missing from their correct locations.  Among these files
were:

twg$tcp:[netdist.include.sys]types.h
twg$tcp:[netdist.include.sys]errno.h
twg$tcp:[netdist.include.sys]netdb.h

I looked all through the [netdist...] directory tree for these files and could
not find them.  I took a look on the directory tree of an older version of
WIN/TCP (v3.2) and found files with the same name (sys/types2.h in v3.2 was
identical to the same file in v5.1, so I assumed the rest would be the same.
Is this a bad assumption) so I copied them to the appropriate location in the
v5.1 directory tree.

After copying these files, I was able to compile CLIENT.C and SERV.C, but got
the following warning in the process:

        typedef long    size_t;
%CC-W-DUPDEFINITION, Duplicate definition of "size_t".
                At line number 41 in TWG$TCP:[NETDIST.INCLUDE.SYS]TYPES.H;1.

Is this a bad thing?

Now, on to the linkage part...

As was suggested in the "Compiling, Linking and Running Network Code" section
of the manual, I added the following definitions to my login.com file to
make the link steps a little easier:

$ define lnk$library sys$library:vaxcrtl.olb
$ define lnk$library_1 tcp:[netdist.lib]libnet.olb
$ define lnk$library_2 tcp:[netdist.lib]libnetacc.olb

and then linked the two programs:

$ link serv
$ link client

When I linked CLIENT, though I was informed of some undefined symbols:

%LINK-W-NUDFSYMS, 2 undefined symbols:
%LINK-I-UDFSYM,         _$EMUL
%LINK-I-UDFSYM,         _$MOVE

These symbols seem to be referenced extensively by modules SELECT, SEND,
RECEIVE, and WRITEV in LIBNETACC...

In fact, when you run the CLIENT program, it dies with an access violation in
the 1st library call (gethostbyname) in the program.

The SERV program is silent.  (I did a $run/det serv, as instructed by the
Programming Guide) The process it is in is still soundly sleeping, no real way
to know whether or not it is working until I can get the client part going.

Does anyone have any suggestions for me?  Is the problem because I copied the
OLD include files?  Maybe there's some special instructions for linking the
new stuff under VMS v4.7?  Maybe it's something else?  Thanks in advance for
any help y'all might be able to lend me here... All I want to do is get some
experience with writing client/server applications, and I can't even get
started yet... Grrr...  Take care, all...

+-------------------------------------+--------------------------------------+
| Joel J. Garrett, Research Associate |         Phone: (302)-451-2332        |
|   Center for Composite Materials    |   inet:  garrett@oscar.ccm.udel.edu  |
|       University of Delaware        |                - or -                |
|       Newark, Delaware 19716        |          garrett@udel.edu            |
+-------------------------------------+--------------------------------------+