head	2.7;
access;
symbols
	3_0_1:2.7
	3_0_0:2.5
	3_0-pre6:2.4
	3_0-pre5:2.4
	3_0-pre4:2.4
	beta15:1.10
	beta14:1.10
	beta13:1.10
	beta12:1.9
	beta11:1.9
	beta10:1.8
	3_0-pre3:2.4
	3_0-pre2:2.4
	3_0-pre1:2.4
	beta21:2.4
	beta20:2.4
	beta19:2.4
	beta18:2.4
	beta17:2.2
	beta16:2.0;
locks;
comment	@# @;


2.7
date	96.10.08.23.19.38;	author hzoli;	state Exp;
branches;
next	2.6;

2.6
date	96.08.22.20.58.47;	author hzoli;	state Exp;
branches;
next	2.5;

2.5
date	96.08.12.04.11.47;	author hzoli;	state Exp;
branches;
next	2.4;

2.4
date	96.05.21.19.39.16;	author hzoli;	state Exp;
branches;
next	2.3;

2.3
date	96.05.17.18.37.45;	author hzoli;	state Exp;
branches;
next	2.2;

2.2
date	96.05.05.00.08.01;	author hzoli;	state Exp;
branches;
next	2.1;

2.1
date	96.05.05.00.04.15;	author hzoli;	state Exp;
branches;
next	2.0;

2.0
date	96.05.02.22.57.04;	author hzoli;	state Exp;
branches;
next	1.12;

1.12
date	96.05.01.08.17.19;	author coleman;	state Exp;
branches;
next	1.11;

1.11
date	96.04.27.01.22.45;	author coleman;	state Exp;
branches;
next	1.10;

1.10
date	95.12.21.22.41.27;	author coleman;	state Exp;
branches;
next	1.9;

1.9
date	95.08.29.01.48.42;	author coleman;	state Exp;
branches;
next	1.8;

1.8
date	95.05.02.08.08.13;	author coleman;	state Exp;
branches;
next	1.7;

1.7
date	95.03.31.21.18.52;	author coleman;	state Exp;
branches;
next	1.6;

1.6
date	95.03.16.01.12.24;	author coleman;	state Exp;
branches;
next	1.5;

1.5
date	95.03.14.01.16.11;	author coleman;	state Exp;
branches;
next	1.4;

1.4
date	95.01.24.04.57.34;	author coleman;	state Exp;
branches;
next	1.3;

1.3
date	94.11.16.06.18.45;	author zsh;	state Exp;
branches;
next	1.2;

1.2
date	94.09.28.02.38.50;	author zsh;	state Exp;
branches;
next	1.1;

1.1
date	94.08.24.00.44.10;	author zsh;	state Exp;
branches;
next	;


desc
@MACHINES
@


2.7
log
@spell fixes from Geoff (2190)
@
text
@
These are the architectures that zsh has been tried on.  If you
succeed in getting zsh to work on an architecture not listed, let
us know.

Apple:	Mac with MiNT after redefining the zgetwd() function as getwd()

Data General: various AViiONs running DG/UX 5.4R3.10 MU01
	Should build `out-of-the-box'.

DEC:	Alpha with Ultrix
	DECstation with Ultrix
	DECstation 5000/25 with Mach 3.0
	Alpha with OSF/1 1.2, 1.3 and 2.0

	In OSF/1 3.x, there is apparently a bug in the header file
	/usr/include/rpcsvc/ypclnt.h; the prototype for yp_all() has a
	struct ypall_callback as its final argument, which should be a
	pointer (struct ypall_callback *).  This prevents compilation
	of one of zsh' files (zle_tricky.c).  If you can't modify the
	header file, create a directory called `rpcsvc' in zsh's Src
	subdirectory and put a fixed version of the header file to it
	before compiling.

	The strip coming with gcc-2.7.2 seems to create unusable
	binaries.  This problem is not related to zsh.  If you have such
	problems, remove the bogus strip and use /bin/strip instead.

DYNIX/ptx 1.4 and 2.0.4 with X11

HP:	HP-UX 9
	Should build `out-of-the-box'.

IBM:	AIX
	Should build `out-of-the-box'.

Linux:	If you are using an early minor version of libc 5, then a bug
	in the auto-configuration process may cause zsh to think that
	your system doesn't support the lstat function.  If the
	configure process reports that there is no lstat, edit
	config.h and change HAVE_LSTAT to 1.
	libc-5.2.18 or later does not have this problem.

	If you create a symbolic link from /dev/fd to /proc/self/fd, zsh
	will use this for process substitution.  This link must exist
	according to the Linux standards but some distributions come
	without it.

NetBSD:	NetBSD 1.x
	Should build `out-of-the-box'.

Next:	NextStep 3.x
	Zsh should build easily on NextStep, but the zsh
	malloc routines are not recommended.

SCO:

SGI:	IRIX 5.1.1.1 and 5.2
	Should build `out-of-the-box'.

Sony:	NWS with NEWS-OS 3.3

SUN:	SunOS 4.1.x
	Should build `out-of-the-box'.
	Under 4.1.3 if yellow pages is used, username completion
	may cause segmentation violation.  This is a bug in the
	shared library not in zsh.  Some libc.so.1.9.x has this
	bug (it fails in yp_all).  Statically linked binaries will
	work if linked with libc.so.1.8.1 (which means that if
	you can get a statically linked binary compiled under 4.1.2
	that it will probably work).
	An alternative but untested solution may be to undefine
	HAVE_NIS in config.h.  This may work, but the first username
	completion will be _very_ slow (as slow as in tcsh).

	Solaris 2.x
	The UCB versions of the routines for reading directories are
	not usable (the struct definitions are incompatible with the
	ones assumed by zsh).  The symptom of this is that globbed
	filenames in the compiled version of zsh will be missing the
	first two letters.  To avoid this, make sure you compile zsh
	without any reference to /usr/ucblib in your LD_LIBRARY_PATH.
	You can easily do this by just unsetting LD_LIBRARY_PATH
	before building zsh.

@


2.6
log
@better description of the OSF/1 header bug workaround
@
text
@d25 1
a25 1
	The strip comming with gcc-2.7.2 seems to create unusable
d27 1
a27 1
	problems, remove the bogous strip and use /bin/strip instead.
d66 1
a66 1
	may cause segmentation violaton.  This is a bug in the
d72 1
a72 1
	An altermative but untested solution may be to undefine
d74 1
a74 1
	completion will be _very_ solw (as slow as in tcsh).
@


2.5
log
@# a really minor change
@
text
@d21 3
a23 3
	header file, copy it to the current directory, modify that
	copy, and put a `-I.' argument into CFLAGS in Makefile for
	the Src subdirectory when compiling.
@


2.4
log
@note that /dev/fd must be a link to /proc/self/fd on Linux
@
text
@d16 1
a16 1
	In OSF/1 3.0, there is apparently a bug in the header file
@


2.3
log
@Note about GNU strip bug on OSF/1
@
text
@d44 5
@


2.2
log
@Some notes about Linux.
@
text
@d25 4
@


2.1
log
@SunOS 4.1.3 yp_all bug description
@
text
@d38 1
@


2.0
log
@New maintainer: Zoltn Hidvgi <hzoli@@cs.elte.hu>
@
text
@d55 10
@


1.12
log
@*** empty log message ***
@
text
@@


1.11
log
@update entry for Linux.  From Bas.
@
text
@d30 1
a30 1
IBM:	AIX 3.2
@


1.10
log
@*** empty log message ***
@
text
@d33 5
a37 5
Linux:	If your Linux is using libc with version >= 5, then
	a bug in the auto-configuration process will cause
	zsh to think your system doesn't support the lstat
	function.  So after running `configure', you should
	edit config.h, and change HAVE_LSTAT to 1.
@


1.9
log
@*** empty log message ***
@
text
@d1 4
a4 2
These are the architectures that zsh has been tried on.  If you succeed
in getting zsh to work on an architecture not listed, let us know.
d9 1
a9 1
		The zsh malloc routines work just fine.
d11 2
a12 4
DEC:	Alpha with OSF/1 1.2, 1.3 and 2.0
	Alpha with Ultrix (unspecified)
	DECstation with Ultrix (unspecified)
	DECstation 5000/240 with Ultrix 4.2A
d14 10
a26 1

d28 1
a28 2
		Builds out of the box with both HP compiler and
		gcc 2.5.8.
d31 1
d33 14
a46 13
Linux:
		The zsh malloc routines are usable on Linux.
		If your Linux is using libc with version >= 5, then
		a bug in the auto-configuration process will cause
		zsh to think your system doesn't support the lstat
		function.  So after running `configure', you should
		edit config.h, and change HAVE_LSTAT to 1.

NetBSD:	NetBSD 1.0

Next:	NextStep 3.0, 3.1, 3.2
		The zsh malloc routines are not recommended
		for use on the Next.
d49 1
d53 12
a64 6
SUN:	SunOS 4.1.1, 4.1.3
		Builds ok with native cc and gcc 2.5.8.
	Solaris 2.1, 2.2, 2.3, 2.4
		Builds ok with both gcc 2.5.8, and SPARCompiler 3.01.
		When building zsh on Solaris, you should unset your
		LD_LIBRARY_PATH environment variable.
@


1.8
log
@*** empty log message ***
@
text
@d25 6
a30 2
		The zsh malloc routines are now usable on Linux.
		Otherwise, should build out of the box.
d32 1
a32 1
NetBSD:	NetBSD 0.9b, 1.0
d44 1
a44 1
	Solaris 2.1, 2.2, 2.3
@


1.7
log
@*** empty log message ***
@
text
@d18 3
a20 1
HP:
d26 1
@


1.6
log
@*** empty log message ***
@
text
@d6 3
@


1.5
log
@*** empty log message ***
@
text
@d15 1
a15 4
HP:	HP9000/700, after manually telling buildzsh to use setpgid
	HP9000/827, but only with GCC
	HP9000/847
	HPUX 9.04
d20 1
a20 2
		The zsh malloc routines are not recommended
		for use on Linux.
@


1.4
log
@*** empty log message ***
@
text
@d1 2
a2 3
These are the architectures that zsh has been tried on.
If you succeed in getting zsh to work on an architecture
not listed, let us know.
d39 3
a41 3
		Builds ok with both gcc 2.5.8, and SunSoft cc.
		When building zsh on Solaris, do not put the directory
		/usr/ucblib in your LD_LIBRARY_PATH.
@


1.3
log
@*** empty log message ***
@
text
@d27 1
a27 1
NetBSD:	NetBSD 0.9b
d29 1
a29 1
Next:	NextStep 3.0,3.1,3.2
@


1.2
log
@*** empty log message ***
@
text
@d37 1
a37 1
SUN:	SunOS 4.1.1 and 4.1.3
d39 1
a39 1
	Solaris 2.1,2.2,2.3
d41 2
a42 3
		You shouldn't have /usr/ucblib in your LD_LIBRARY_PATH,
		use /usr/lib instead.
		You should have /usr/bin before /usr/ucb in your PATH.
@


1.1
log
@Initial revision
@
text
@d23 3
a25 1
Linux:	(various versions), but can't use USE_ZSH_MALLOC
d38 1
a38 3
		"buildzsh auto" ok
		"buildzsh auto gcc" ok with gcc 2.5.8
		fine with gcc 2.5.8.
d40 4
a43 2
		"buildzsh auto" ok
		"buildzsh auto gcc" ok with gcc 2.5.8
@
