install.ms.1

早期freebsd实现

FUNCTYPE	int
HAVE_ST_BLKSIZE	DONT
HAVE_TM_GMTOFF	DONT
LDFLAGS	
LINTFILTER	| sed -n -f ../sedf.aix
LINTFLAGS	-wkD -b -h $(DEFS)
LINTLIBSTYLE	SYSV
LOCK_STYLE	FNCTL
MISSING_MAN	
MISSING_SRC	
NEED_TIME	DO
POINTER	void
.DE
Under AIX 3.1, you must also use the \fIsyslog\fP that comes with INN.
This is not necessary for 3.2.
Some versions also need \USE_UNION_WAIT\fP set to ``DONT''.
.PP
.DS
.UL "A/UX"
.ta \w'HAVE_ST_BLKSIZE   'u
LIBS	-lbsd
.DE
Make sure you don't use \fIgcc\fP version 1; it miscompiles the socket calls
in \fIinnd/cc.c\fP.
.PP
.DS
.UL "BSDI"
ABORTVAL	void
ALARMVAL	u_int
EXITVAL	volatile void
_EXITVAL	volatile void
FREEVAL	void
GETPIDVAL	pid_t
GID_T	gid_t
HAVE_UNISTD	DO
HAVE_VFORK	DONT
HAVE_WAITPID	DO
LSEEKVAL	off_t
MISSING_OBJ	
MISSING_SRC	
_PATH_COMPRESS	/usr/bin/compress
_PATH_EGREP	/usr/bin/egrep
_PATH_MAILCMD	/usr/bin/Mail
_PATH_SENDMAIL	/usr/sbin/sendmail -t
PID_T	pid_t
POINTER	void
QSORTVAL	void
SIZE_T	size_t
SLEEPVAL	u_int
UID_T	uid_t
USE_UNION_WAIT	DONT
VAR_STYLE	STDARGS
.DE
Change the \fISHELL\fP variable in \fIconfig/Makefile\fP and
\fIsite/Makefile\fP to point to \fI/usr/contrib/bin/bash\fP.
Edit \fIlib/Makefile\fP so that the \fIinstall\fP target does not
try to make \fI../llib-linn.ln\fP.
You must also use the GNU \fIsed\fP; the version distributed with
BSDI 0.9.4.1 enters an infinite loop processing newgroup messages.
.PP
.DS
.UL "HP-UX 8.0"
.ta \w'HAVE_ST_BLKSIZE   'u
ABORTVAL	void
ALARMVAL	unsigned int
CLX_STYLE	FCNTL
CTYPE	isXXXXX((c))
DEFS	-I../include -DHPUX
FDCOUNT_STYLE	SYSCONF
FREEVAL	void
GETPIDVAL	pid_t
GID_T	gid_t
HAVE_SETBUFFER	DONT
HAVE_ST_BLKSIZE	DONT
HAVE_TM_GMTOFF	DONT
HAVE_UNISTD	DO
HAVE_WAITPID	DO
LINTFILTER	| sed -n -f ../sedf.sysv
LINTFLAGS	-b -h $(DEFS)
LINTLIBSTYLE	SYSV
LOCK_STYLE	LOCKF
LOG_INN_PROG	LOG_LOCAL7
LOG_INN_SERVER	LOG_LOCAL7
LSEEKVAL	off_t
_PATH_MAILCMD		/usr/bin/mailx
NOFILE_LIMIT	200
PID_T	pid_t
POINTER	void
PROF	
QSORTVAL	void
RANLIB	echo
RES_STYLE	TIMES
SIZE_T	size_t
SLEEPVAL	unsigned int
UID_T	uid_t
USE_UNION_WAIT	DONT
_EXITVAL	void
.DE
You will probably also need to use the \fIbdf\fP command instead of \fIdf\fP.
.PP
.DS
.UL "SGI Indigo with IRIX 4.0.1"
.ta \w'HAVE_ST_BLKSIZE   'u
ABORTVAL	void
ALARMVAL	uint
ACT_STYLE	MMAP
CFLAGS	$(DEFS) -g -w
CLX_STYLE	FCNTL
_EXITVAL	void
FORK	fork
FREEVAL	void
GID_T	gid_t
HAVE_ST_BLKSIZE	DONT
HAVE_TM_GMTOFF	DONT
HAVE_UNISTD	DO
LDFLAGS	
LIBS	-lmld
LINTFILTER	| sed -n -f ../sedf.sysv
LINTFLAGS	 $(DEFS)
LINTLIBSTYLE	SYSV
LSEEKVAL	off_t
POINTER	void
QSORTVAL	void
RANLIB	echo
SIZE_T	size_t
SLEEPVAL	uint
UID_T	uid_t
_PATH_COMPRESS	/usr/bsd/compress
.DE
Also, the \fIMISSING_xxx\fP parameters should be empty.
.PP
.DS
.UL "Solaris 2.X/SunOS 5.X, using SPARCompiler C 2.X"
.ta \w'HAVE_ST_BLKSIZE   'u
DEFS	-I../include -DSUNOS5
USE_CHAR_CONST		DO
CFLAGS	-O -Xa $(DEFS)
LDFLAGS
LIBS	-lnsl -lsocket -lelf
LINTLIBSTYLE	SYSV
LINTFLAGS	-b -h $(DEFS)
LINTFILTER	| sed -n -f ../sedf.sysv
RANLIB	echo
VAR_STYLE	STDARGS
SIZE_T	size_t
UID_T	uid_t
GID_T	gid_t
PID_T	pid_t
POINTER	void
ALIGNPTR	long
LOCK_STYLE	LOCKF
HAVE_UNISTD	DO
HAVE_SETSID	DO
HAVE_TM_GMTOFF	DONT
HAVE_WAITPID	DO
USE_UNION_WAIT	DONT
HAVE_VFORK	DONT
HAVE_UNIX_DOMAIN	DONT
CLX_STYLE	FCNTL
RES_STYLE	TIMES
FDCOUNT_STYLE	SYSCONF
ABORTVAL	void
ALARMVAL	unsigned
GETPIDVAL	pid_t
SLEEPVAL	unsigned
QSORTVAL	void
LSEEKVAL	off_t
FREEVAL		void
_EXITVAL	void
MISSING_SRC		
MISSING_OBJ		
PATH_COMPRESS	/bin/compress
.DE
Make sure you use the C version of subst.
.PP
.DS
.UL "System V Release 4"
.ta \w'HAVE_ST_BLKSIZE   'u
FREEVAL	void
GETPIDVAL	long
HAVE_TM_GMTOFF	DONT
HAVE_WAITPID	DO
LDFLAGS
LIBS	-lnsl -lsocket
LINTFILTER	| sed -n -f ../sedf.sysv
LINTFLAGS	-b -h $(DEFS)
LINTLIBSTYLE	NONE
LOCK_STYLE	FCNTL
MANPAGESTYLE	NONE
MISSING_MAN	strcasecmp.3
MISSING_OBJ	strerror.o strcasecmp.o
MISSING_SRC	strerror.c strcasecmp.c
_PATH_MAILCMD		/usr/bin/mailx
POINTER	void
QSORTVAL	void
RANLIB
RES_STYLE	TIMES
SIZE_T	unsigned int
USE_CHAR_CONST	DONT
USE_UNION_WAIT	DONT
.DE
I was never able to get \fIlint\fP to be useful on the machine I used.
Some versions of System V (for example, Esix 4.0.3) need the following
LIBS value:
.DS
.ta \w'HAVE_ST_BLKSIZE   'u
LIBS	-lresolv -lsocket -lnsl -L/usr/ccs/lib -lelf
.DE
On a Dell System V machine, you have to set \fIHAVE_UNIX_DOMAIN\fP to ``DONT.''
.PP
.DS
.UL "Ultrix 4.x (RISC)"
.ta \w'HAVE_ST_BLKSIZE   'u
ALARMVAL	unsigned int
FREEVAL	void
LDFLAGS
LINTFILTER	| sed -n -f ../sedf.sysv
LINTFLAGS	-b -u -x $(DEFS)
LSEEKVAL	off_t
MISSING_MAN	
MISSING_OBJ	syslog.o strerror.o
MISSING_SRC	syslog.c strerror.c
POINTER	void
PROF	-p
QSORTVAL	void
SIZE_T	unsigned int
SLEEPVAL	unsigned int
_EXITVAL	void
.DE
Ultrix also requires the new \fIsyslog\fP.
Some sites have reported problems with using the \fIsyslog\fP that INN includes.
The file \fIjtkohl-syslog-complete.tar.Z\fP in the \fI/pub/DEC\fP
directory on gatekeeper.dec.com has a ``for-Ultrix'' package that handles
both old and new \fIsyslog\fP calls.
While Ultrix has symlinks, it does not have the ``\-follow'' option in
its \fIfind\fP command.
This is used in \fIexpire/makeactive.c\fP; you will have to either install
the GNU \fIfind\fP or edit the source file.
.NH 1
Other Source Preparations
.PP
In addition to setting up the configuration file, it might be necessary
to do some other setups.
.NH 2
Systems with old syslogs
.PP
If you need to install the \fIsyslog\fP that is distributed with INN, go to
the top of the distribution and type ``make syslogfix''.
This will also compile \fIsyslogd\fP, the logging daemon.
You should install this to replace your existing daemon, usually in
\fI/etc/syslog\fP.
You will also need to install the new-style \fIsyslog.conf\fP file.
.PP
If you cannot replace \fIsyslogd\fP on your machine, then see the file
\fIsyslog/README\fP for information on how to set it up as an alternate
daemon.
.PP
Ignore any complaints from \fIlint\fP about the INN sources calling
\fIopenlog\fP with the wrong argument count.
In fact, if you \fBdon't\fP get any complaints, then something is wrong
with the way \fIsyslog\fP, \fI<syslog.h>\fP, or the \fIlint\fP libraries
are set up on your system.
.NH 2
The DBZ package
.PP
INN uses the DBZ database package.
Thanks to Jon Zeeff for his permission to use and redistribute DBZ,
as modified by Henry Spencer. 
INN has its own set of modifications to DBZ.
The changes are made with the \fIpatch\fP program and the context diff
in \fIlib/dbz.pch\fP.
If you don't have \fIpatch\fP installed, then you can make the changes
manually.
(If you don't have Larry Wall's \fIpatch\fP program get it from any
\fIcomp.sources.unix\fP archive as well as many FSF archives and other
places \(em you'll be glad you did.)
.PP
If you are using \fIvfork\fP (specified in the \fIFORK\fP parameter),
or you want to \fImmap\fP the database, then you \fBmust\fP apply the patch.
The Makefile in \fIlib\fP will normally do it for you automatically, anyway.
The beginning of the patch file describes the changes made in more detail.
If you do not apply the patch, then you must add add ``dbzalt.c'' and
\&``dbzalt.o'' to the MISSING_SRC and MISSING_OBJ parameters.
.PP
Apparently the System V 386 compiler can't optimize \fIdbz.c\fP (the
GNU C compiler doesn't have this problem).
If you have ``\-O'' in your \fIDBZCFLAGS\fP configuration parameter, then
take it out.
.NH 2
Using writev
.PP
INN makes extensive use the \fIwritev\fP system call to write several
I/O buffers in a single call.
If you do not have \fIwritev\fP then you must copy \fIinclude/uio.h\fP to
your \fI/usr/include/sys\fP directory.
You must also add ``writev.c'' and ``writev.o'' to the MISSING_SRC and
MISSING_OBJ parameters.
.PP
The ``fake'' \fIwritev\fP found in the \fIlib\fP directory is not highly
efficient.
You might want to write a better one that tries to \fImalloc\fP a new
buffer and join all the elements.
Be careful about doing this because \fIinnd\fP can use very big buffers.
.NH 1
Compiling the System
.PP
Once the INN sources have been configured, they are ready to be compiled.
If you are very confident of your changes, type the following:
.DS
cd $inn
make all
.DE
If you do not get any errors, skip to the section titled ``Installing the
System.''
.PP
If you are confident, but careful, type:
.DS
cd $inn
make world
cat */lint
.DE
This will compile everything, then run \fIlint\fP in all directories.
.PP
Another option is to run the \fIBUILD\fP script found at the top of
the source tree.
This will interactively configure, compile, and install the system.
After running that script, skip to the section titled ``Installing the
System.''
.PP
If you are more cautious, you should type the following:
.DS
cd $inn/config
make quiet
cd ..
.DE
This will use your already-tested \fIsubst\fP program with your new
\fIconfig.data\fP file.
You should then follow the steps in the following sections.
.NH 2
Building the Library
.PP
The next step is to build the INN library.
Do the following
.DS
cd $inn/lib
make libinn.a lint
.DE
.PP
This will build the library and run \fIlint\fP on the sources, putting
the output into a file named \fIlint\fP.
If anything fails to compile, you probably made a configuration error,
most likely in the ``C library differences'' section.
In particular, double-check the \fISIGHANDLER\fP and \fIxxx_STYLE\fP
parameters.
.PP
The \fIlint\fP output should be almost empty, except for a couple of
\&``possible pointer alignment problem'' warnings in \fIdbz.c\fP.
If you get much more than this, then you probably did not define
the \fIPOINTER\fP or \fISIZE_T\fP parameters properly.
The \fINEW\fP and \fIRENEW\fP macros in \fIinclude/macros.h\fP try to
capture all the alignment problems associated with dynamic memory allocation.
Also double-check the \fIALIGNPTR\fP parameter and the \fICAST\fP macro in
\fIinclude/macros.h\fP.
.PP
If \fIlint\fP reports any other problems, you should take the time to
investigate them.
Note that many \fIlint\fP libraries have errors.
Also, you may get some problems in \fIyaccpar\fP in \fIparsedate.y\fP; these
are most likely in the \fIyacc\fP-generated C code.
If you get any of these, complain to your vendor.
.PP
If you find a portability issue that I missed, please let me know.
.PP
Once the library is built, you should install it in the top-level INN
directory.
To do this type ``make\ install'' while still in the \fIlib\fP directory.
This will also compile a \fIlint\fP library for use in linting the programs
in the other directories.
.PP
Note that any time a change is made to the library you must do
\&``make\ install''; it is not enough to type ``make\ libinn.a''.
This is a deliberate decision \(em like a program, compiling a library
is different from making it available for others to use, and installing
a library should make it possible to run \fIlint\fP against it.
.NH 2
Compiling the Programs
.PP
INN's programs are separated into six areas, as detailed in the roadmap.
You'll need to build each one before you can install and use INN.
.NH 3
The Frontend Programs
.PP
Frontends are those programs that talk to the main news server, either
offering it articles or controlling its action.
This includes the following programs:
.IP \fIinews\fP 15
The program that validates and prepares news articles and gives them to
\fIinnd\fP.
This is mostly used by users (usually indirectly, through programs like
\fIPnews\fP), but also through special facilities such as news/mail