> Perhaps tcpserver or the docs are just intimidating. I know I was a bit
> reluctant to use it at first, now I find myself using it for just about
> everything - including backups, passing encrypted data between hosts, etc.
> It's really handy! Thanks Dan!!
Example:
ucwhatever INSTALL instructions:
spy [4246]> less INSTALL
Like any other piece of software (and information generally), ucspi-tcp
comes with NO WARRANTY.
Things you have to decide before starting:
* The ucspi-tcp home directory, normally /usr/local. To change this
directory, edit conf-home now.
How to install:
1. Compile the programs and create the formatted man pages:
% make
2. Install the programs and man pages:
# make setup check
That's it! To report success:
% ( echo 'First M. Last'; cat `cat SYSDEPS` ) | mail [EMAIL PROTECTED]
Replace First M. Last with your name.
chmod 755 compile
./compile tcpclient.c
./compile: cc: not found
*** Error code 1
make: Fatal error: Command failed for target `tcpclient.o'
spy [4228]> cat compile
#!/bin/sh
# WARNING: This file was auto-generated. Do not edit!
exec cc -O2 -c ${1+"$@"}
Where does it say edit conf-cc and conf-ld ?
if I cat compile -- it says "cc" but that file is generate?
Of course, I could do something like:
spy [4250]> egrep -i "conf\-cc" *
FILES:conf-cc
Makefile:warn-auto.sh conf-cc
Makefile: echo exec "`head -1 conf-cc`" '-c $${1+"$$@"}' \
Makefile:recordio.c argv0.1 argv0.c rts.sh rts.tests rts.exp conf-cc conf-ld \
Makefile:find-systype.sh conf-cc conf-ld trycpp.c
Makefile: echo CC=\'`head -1 conf-cc`\'; \
and see that games being played with conf-cc ...
but then ld will fail, and I'll have to do the same for that after
the make fails.
Why not mention *this* in this INSTALL?
How many people here had to ask or figure this out for
themselves provided that they didn't have "cc" working?
Scott
