home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sgi
- Path: sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!jvnc.net!darwin.sura.net!mips!odin!chef.reading.sgi.com!walton_a
- From: walton_a@chef.reading.sgi.com (Andrew Walton)
- Subject: Re: Need help with RPC on Indigo
- Message-ID: <1992Aug21.084627.26342@odin.corp.sgi.com>
- Keywords: RPC
- Sender: news@odin.corp.sgi.com (Net News)
- Nntp-Posting-Host: chef.reading.sgi.com
- Organization: Silicon Graphics, Inc.
- References: <1992Aug20.211112.19527@u.washington.edu>
- Distribution: na
- Date: Fri, 21 Aug 1992 08:46:27 GMT
- Lines: 27
-
- I tried the msg_server example in the 4.0.1 manual and hit similar
- problems, when I checked the my old 3.3.3 manual I found the arguments
- to the remote calls were reversed, they should be
-
- result = remote_1(&argument, client)
-
- in the 4.0.1 manual for some reason they are
-
- result = remoye_1(client, &argument)
-
- If you are using rpcgen you can get it to create prototypes with the
- -P option but I think there is a bug lurking in there.
-
- try rpcgen -P on the following rpc spec
-
- program STRING_TEST {
- version VERSION {
- int function(string) = 1;
- } = 100;
- } = 200;
-
- The C code generated has char ** for the argument pointer, but the
- protottype has string * for the argument pointer and string doesn't
- appear to be defined in any of the rpc header files. It looks like
- simple text substitution is used to generate the prototypes.
-
-
-