Lines Matching +full:in +full:- +full:built

8 This distribution contains SunSoft's implementation of transport-independent
9 RPC (TI-RPC), External Data Representation (XDR), and various utilities and
15 transport-specific RPC (TS-RPC).
17 TI-RPC is an enhanced version of TS-RPC that requires the UNIX System V
19 (XTI).  TI-RPC is on-the-wire compatible with the TS-RPC, which is supported
20 by almost 70 vendors on all major operating systems.  TS-RPC source code
24 building on Solaris 2.3.  This release was built on Solaris 2.3 using SunPro
29 that are assumed may not be available.  In particular, this release uses the
31 routines use the Solaris Name Service Switch to access public-key credential
34 interfaces of UI Threads to make certain interfaces thread-safe.  These
35 interfaces are found in libthread in Solaris 2.3 and later.
38 States domestic version of libcrypt in order to resolve the cbc_crypt() and
42 within the United States.  (PLEASE NOTE: The RPC implementation found in
49 The documentation found in the doc directory are derived from the Solaris 2.3
51 given, and these use libnsl to link in the RPC library.  This release builds
53 "-lrpc -lnsl -lcrypt".  This links the application with TIRPCSRC 2.3's librpc
61 technologies available for reference and porting to non-Solaris platforms.
64 library in libnsl, rpcbind, rpcinfo, etc.).  It is not our intention to
69 WHAT'S NEW IN THIS RELEASE: TIRPCSRC 2.3
77 2.      The RPC library is thread safe for all client-side interfaces
78 	(clnt_create, clnt_call, etc.).  The server-side interfaces
79 	(svc_create, svc_run, etc.) are not thread safe in this release. The
80 	server-side interfaces will be made thread safe in the next release of
84 3.      As part of the work to make the RPC library thread-safe, rpcgen has
85 	been enhanced to generate thread-safe RPC stubs (the -M option).  Note
86 	that this modifies the call-signature for the stub functions; the
92 	first introduced in TIRPCSRC 1.0, and was bundled with librpc.  It is
94 	can be achieved by using threads for making client-side RPC calls.
130 to be the path to the top-level Makefile.  For example, if /usr/src/tirpcsrc
131 is where to top-level Makefile is located, execute this command prior to
138 The sources in the lib directory depend on header files installed from head
139 and uts/common/rpc, and the programs in the cmd directory depend on libraries
142 The top-level Makefile builds the release.  The "ROOT" macro defines where the
150 The headers, libraries and executables will be built and installed under the
154 The demonstration services in the demo directory are not built by the
155 top-level "make install" command.  To build these, cd to the cmd/demo
156 directory and enter "make".  The four services will be built.
157 RPCGEN MUST BE INSTALLED in a path that make can find.  To run the
159 (you probably will want to put it in the background).  rpcinfo can be
160 used to check that the service succeeded in getting registered with
167 See the Makefiles in the demonstration services for examples of building
169 must be included in the compiler header file search path (-I), and the
170 $(ROOT)/usr/lib directory must be included in the linker library file search
171 path (-L).  Also, to run executables built dynamically, the shared library
172 search path (LD_LIBRARY_PATH) must also include $(ROOT)/usr/lib.  In addition
173 to linking in this release's librpc (via -lrpc), you must also link with
174 Solaris's libnsl (-lnsl) and the US domestic version of libcrypt (-lcrypt).