-*- mode: Text -*-

		       Cygwin32 Support Files for Flick

		     The Flux Project, University of Utah
		     http://www.cs.utah.edu/projects/flux/
				+1-801-585-3271

				   May 1998


This directory contains files that are not part of Flick, but which you may
need in order to compile and use Flick in a Cygwin32/GNU-Win32 environment.

Cygwin32 is a library that implements a UNIX-like interface for Windows 95 and
Windows NT.  GNU-Win32 is a suite of GNU tools ported to run with Cygwin32.
Both Cygwin32 and GNU-Win32 are available from Cygnus Solutions via the World
Wide Web at <http://www.cygnus.com/>.

CONTENTS ----------------------------------------------------------------------

In this directory you will find:

	README		The file you are reading now.

	include		This directory contains C system header files that are
			required in order to build Flick.  Cygwin32 does not
			contain these files by default.

	libnsl		This directory contains the sources for building a
			minimal `libnsl' library which contains the standard
			set of RPC and XDR functions.  While many systems
			provide these functions in `libc', Cygwin32 does not.

	portmap		This directory contains sources for a portmapper
			daemon.  A portmapper is required in order for one to
			run ONC RPC (Sun RPC)-based servers on a Windows host.

The files within `include' and `libnsl' are derived from corresponding files
within the GNU C Library.  The GNU C Library in turn assimilated these files
from Sun Microsystems' RPCSRC distribution of Sun RPC.  All of the files within
`include' and `libnsl' are freely distributable; some are controlled by the Sun
RPC license and some are controlled by the GNU Library General Public License
(GLPL).  See the notices in the individual files for details.

The files within `portmap' are derived from Weitse Venema's enhanced portmapper
distribution, version 4.  (See the `portmap/README' file.)  All of the files in
the `portmap' directory are freely distributable; some are controlled by the
Sun RPC license and some are controlled by a BSD license.  See the notices in
the individual files for details.

The `portmap' installation notes (below) contain important details about
portmapper security features that are disabled by default under Cygwin32.

All of the support files have been tested with Cygwin32 b18.

INSTALLATION ------------------------------------------------------------------

Installation of the additional support files is manual but simple:

	include		To install the header files, simply copy the files
			within this directory into GCC's system include
			directory.  The complete pathname of GCC's system
			include directory depends on your installation of
			Cygwin32.  You can find your system include directory
			by searching for the file `stdio.h' in your Cygwin32
			installation.  The directory that contains `stdio.h' is
			your system header directory.

			BE CAREFUL to preserve the directory hierarchy of the
			files that you copy into your system header directory.
			For instance, the file `cdefs.h' must be located within
			a `sys' subdirectory of GCC's system header directory,
			so that it can be included as <sys/cdefs.h>.
			Similarly, all of the RPC header files must be located
			within an `rpc' subdirectory.

			ALSO BE CAREFUL not to delete any header files that are
			already installed on your system!  In particular, be
			careful not to delete the files that are already
			contained in the `sys' subdirectory of your Cygwin32
			installation's system header file directory!

	libnsl		To install the `libnsl' library, you must compile the
			libnsl sources with GCC and then copy `libnsl.a' into
			GCC's system library directory.  The Makefile with
			`libnsl' should be sufficient to compile the library.

			Again, the exact pathname of the system library
			directory varies across Cygwin32 installations.  You
			can find your system's library directory by searching
			for the file `libc.a'.  The directory that contains
			`libc.a' is your system library directory.

	portmap		You must compile and install the `libnsl' library
			before you can compile the `portmap' daemon.

			To install the `portmap' daemon, you simply compile the
			portmapper sources with GCC and then copy the resultant
			`portmap' program to some directory in your executable
			search path.  A good location might be the `bin'
			directory within your Cygwin32 tree.

			You may want to install the utility `pmap_dump' and
			`pmap_set' programs in your search path as well.

			Note that you must start the `portmap' daemon on your
			Windows machine before you run any Flick-generated ONC
			RPC (Sun RPC)-based servers on your machine.  (ONC RPC
			servers attempt to register themselves with the
			portmapper.)  To start the portmapper daemon, simply
			run the `portmap' program.  Command line options:

				-d	Prevent portmap from running as a
					daemon, and cause debugging information
					to be printed to stderr.

				-v	Issue verbose logging access control
					checks.

			The `-d' switch may be required under Windows 95.  We
			have had problems running `portmap' as a daemon under
			Windows 95, but haven't really investigated the issue.

			IMPORTANT NOTE: The Cygwin32 version of Weitse Venema's
			`portmap' DOES NOT enable-based host access control by
			default and DOES NOT link with the TCP wrapper library.
			Since these features are among the primary enhancements
			of Weitse Venema's portmapper, it is important that you
			understand that these features are DISABLED by default
			in our Cygwin32 port (because the TCP wrapper library
			is not a standard part of Cygwin32).  If you want to
			restore these important security features, you will
			need to acquire the TCP wrapper library yourself from
			<ftp://ftp.win.tue.nl/pub/security/>, compile it, and
			then modify the `portmap' Makefile to link with your
			wrapper library.

COMPILING FLICK ---------------------------------------------------------------

After you have installed the extra support files into your Cygwin32 setup, you
should be able to compile and use Flick.  Refer to the Flick user's guide or
the `INSTALL' file further instructions.

-------------------------------------------------------------------------------

## End of file.

