Operating System ports of ZSH

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:
Data General:
Should build `out-of-the-box'.
DEC:
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, copy it to the current directory, modify that copy, and put a -I. argument into CFLAGS in Makefile for the Src subdirectory when compiling.

The strip comming 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:
Should build `out-of-the-box'.
IBM:
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:
Should build `out-of-the-box'.
Next:
Zsh should build easily on NextStep, but the zsh malloc routines are not recommended.
SGI:
Should build `out-of-the-box'.
Sony:
SUN:
Should build `out-of-the-box'.