![[prev]](../Images/DocsLeftArrow.gif){kind=small}
![[next]](../Images/DocsRightArrow.gif){kind=small}
![[up]](../Images/DocsUpArrow.gif){kind=small}
![[top]](../Images/DocsContents.gif){kind=small}
These are the OSes that zsh has been tried on. If you succeed in getting zsh to work on an OS not listed, let us know.
On all machines if you use gcc and upgrade your OS you must rebuild gcc after the OS upgrade. A gcc left from a previous OS may seem to work but compiling more complex programs may fail mysteriously.
Should build `out-of-the-box'.
For dynamic loading to work, you need to use the dlcompat library. It can be downloaded from: https://sourceforge.net/projects/fink/files/.
Should build `out-of-the-box'. The compilation directory should be on a file system mounted as binary (the mount command shows `binmode'). There are various issues with Cygwin versions before 1.3.2 - you are adviced to update to the latest release.
Dynamic loading works as of cygwin-1.1.3 and binutils-20000722-1. It was not tested for earlier versions. This does not imply that every module will work. New completion and in particular zsh/zftp and zsh/mathfunc are known to work.
Some of the tests in the Test subdirectory are known to fail: this is because the UNIX environment is not completely implemented.
Cygwin allows mount without existing mount point (e.g. "mount //server/path /usr/src" where /usr/src does not exist). Path completion will fail inside these mounts; make sure that every mount point really exists.
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.
On Digital UNIX 4.0, compilation with gcc and with --enable-dynamic
apparently needs configuring with explicit flags when compiling
with debugging enabled:
DLLD=gcc LDFLAGS='-g -rpath
Should build `out-of-the-box'. On FreeBSD 2.2, dynamic loading does not work, but it does with 3.x and 4.x.
Should build `out-of-the-box'.
Problems with dynamic loading have been reported under 11, but this should compile using the standard dlopen() function set (rather than the 10.20 shl_load() function set). More details of any difficulties would be appreciated.
Compiling with gcc 2.7.1 is known to fail with header file conflicts on HP-UX 11. Use the HP ANSI C compiler.
Should build `out-of-the-box', but --enable-zsh-mem will not work.
On 3.2, for 64-bit integer support you need to compile with gcc, as the native compiler does not support ANSI simultaneously with `long long'. On 4.1, there appear to be problems using --enable-dynamic (the default) with gcc (version was 2.7.2.3) in 4.1, though native cc works. More information about this problem would be appreciated.
It was reported, that at least some 4.x versions have problem with curses - variables boolcodes and some other are declared in term.h but missing is libcurses.a. That makes native compiler very unhappy (GCC 3.0 apparently does not mind). Zsh now defaults to termcap on AIX; any info about this problem is appreciated.
Should build `out-of-the-box'.
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.
Various problems have been reported when using optimisation with the experimental GNU compiler, egcs. In particular, on Linux Alpha with egcs 1.0.3a and 1.1.1 using -O1 or greater, the completion code is not correctly compiled.
Some versions of glibc2 have a conflict with
MX (Intel) platform: SINIX-L/M 5.41
Builds out-of-the-box with EGCS. Neither dynamic loading nor
64-bit integers are supported. Native compiler was not tried
mostly because GCC/EGCS builds out-of-the-box as well. If you
succeed with native compiler, send a patch for this file
to zsh-workers.
RM (MIPS) platform: SINIX-N/Y 5.42
Should build out-of-the-box but it was not tested. Neither
dynamic loading nor 64-bit integers are supported.
Note, that this version is obsolete and users are expected to
update to Reliant UNIX.
Should build `out-of-the-box'.
On 6.5.2, zsh malloc routines are reported not to work; also full optimization (cc -O3 -OPT:Olimit=0) causes problems.
The zpty module is not currently supported.
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.
Problems have been reported using --enable-lfs (the default) to enable large file system and integer support on Solaris 2 with gcc. Apparently upgrading to gcc version 2.95.2 fixes this. If this is not feasible, configure with --disable-lfs. We would be grateful for more detailed information. The most problems seem to occur on Solaris 2.6, where --disable-lfs is recommended.
Zsh has previously been compiled on the following machines, but the developers do not have direct access to them and the reports may be out of date. We would be glad to receive any reports of success or failure on these OS's — and, of course, any others not mentioned in this file.