1----------------------------- 2ZSH ON SPECIFIC ARCHITECTURES 3----------------------------- 4 5These are the OSes that zsh has been tried on. If you succeed in getting 6zsh to work on an OS not listed, let us know. The information in this 7list may be out of date, as the developers do not have access to all 8machines. In general, GNU/Linux distributions, Solaris and Cygwin are 9reasonably well covered. Please let us have any recent information 10on other systems. The information for systems not known to have been 11tested recently is marked as `out of date'. 12 13On all machines if you use gcc and upgrade your OS you must rebuild gcc 14after the OS upgrade. A gcc left from a previous OS may seem to work 15but compiling more complex programs may fail mysteriously. 16 17The format of entries is thus: 18 19 Vendor: OS & version (hardware type) [zsh version tried] 20 information 21 22Machines 23-------- 24 25Apple: MacOS X/Darwin 10.x 26 Should build `out-of-the-box'. 27 28 For dynamic loading to work on 10.1 and 10.2, you need to use the 29 dlcompat library. It can be downloaded from: 30 http://sourceforge.net/project/showfiles.php?group_id=17203 31 32 The zsh/zpty library is not working on 10.1 and 10.2, but is on 33 10.3. This causes the tests starting `Y' in the Test directory to 34 fail, even though the features to be tested are working. 35 36 Reported to compile with no problems on 10.4. 37 38 Multibyte support works; you probably wish to set the 39 option COMBINING_CHARS, which is not enabled by default. 40 Problems have been noted when outputting multibyte characters 41 to the terminal from a "preexec" function. 42 43Red Hat Inc.: Cygwin 44 Should build `out-of-the-box'. The compilation directory should 45 be on a file system mounted as binary (the mount command shows 46 `binmode'). There are various issues with Cygwin versions before 47 1.3.2 - you are adviced to update to the latest release. 48 49 Process substitution using <(...), >(...), =(...) may be 50 problematic. Different versions of zsh and Cygwin have 51 a different mix of issues. 52 53 Problems handling subprocesses have been reported with Cygwin 54 1.7.5. It is not currently known how the problems split between 55 Cygwin and zsh. 56 57 Some of the tests in the Test subdirectory are known to fail: 58 this is because the UNIX environment is not completely implemented. 59 60 Cygwin allows mount without existing mount point (e.g. 61 "mount //server/path /usr/src" where /usr/src does not exist). 62 Path completion will fail inside these mounts; make sure that 63 every mount point really exists. 64 65FreeBSD: FreeBSD 2.2.7, 3.x, 4.x, ... 7 66 Should build `out-of-the-box'. On FreeBSD 2.2, dynamic loading 67 does not work, but it does with 3.x and later. 68 69HP: HP-UX 9, 10.20, 11.x (PA-RISC, Itanium) 70 Should build `out-of-the-box'. 71 72 Previous problems encountered on HP-UX 11.x: 73 74 Some of the special keys on the keyboard (backspace, delete) 75 have been found to stop functioning. One suggested fix is 76 to alter the way the curses library is linked in the Makefile. 77 Replacing `-lcurses' with `-lHcurses -lcurses' in the libraries 78 is reported to fix this on 11.0, but is no longer necessary on 79 more recent versions of HP-UX 11, i.e. 11.11+. 80 81 Typical gcc installations on HP-UX use HP's linker rather than 82 the GNU one. Configure will fail to set up dynamic linking in 83 this situation. The following should allow building of modules: 84 DLLD=/usr/ccs/bin/ld DLLDFLAGS=-b DLCFLAGS=-fpic ./configure ... 85 86 Compiling with gcc 2.7.1 is known to fail with header file 87 conflicts. Use the HP ANSI C compiler. 88 89IBM: AIX 3.2, 4.x, 5.x 90 Should build `out-of-the-box'. 91 92 Certain features will not work, in particular --enable-cap 93 and --enable-zsh-mem. (The feature enabled by --enable-cap 94 is apparently present, however. Help getting this to work 95 would be appreciated.) 96 97 On 3.2, for 64-bit integer support you need to compile with gcc, as 98 the native compiler does not support ANSI simultaneously with 99 `long long'. On 4.1, there appeared to be problems using 100 --enable-dynamic (the default) with gcc (version was 2.7.2.3), 101 though native cc works. More information about this problem 102 would be appreciated. 103 104 It was reported, that at least some 4.x versions have problem 105 with curses - variables boolcodes and some other are declared 106 in term.h but missing is libcurses.a. That makes native compiler 107 very unhappy (GCC 3.0 apparently does not mind). Zsh now defaults 108 to termcap on AIX; any info about this problem is appreciated. 109 110Linux: Linux 2.x, 3.x (various 32-bit and 64-bit processors) 111 Should build `out-of-the-box'. 112 113 The following problems should not occur with recent 114 distributions. 115 116 If you are using an early minor version of libc 5, then a bug 117 in the auto-configuration process may cause zsh to think that 118 your system doesn't support the lstat function. If the configure 119 process reports that there is no lstat, edit config.h and change 120 HAVE_LSTAT to 1. libc-5.2.18 or later does not have this problem. 121 122 Some versions of glibc2 have a conflict with <asm/resource.h> 123 which causes a redefinition warning on RLIM_INFINITY. This 124 causes configure to decide that <sys/resource.h> is not present, 125 which can cause compilation errors in zsh's rlimit code. The 126 best solution is to edit config.h after running configure and 127 #define HAS_SYS_RESOURCE_H. 128 129NetBSD: NetBSD 1.x 130 Should build `out-of-the-box'. 131 132OpenBSD: OpenBSD 2.x, 3.x 133 Should build `out-of-the-box'. 134 135OpenIndiana: OpenIndiana 151a 136 Problems have been reported with awk when used to generate 137 prototype files for building zsh. Upgrading to gawk (GNU awk) 138 version 4.0.0 fixes this. 139 140Sun: Solaris 2.x, 8, 9, ... 141 It is recommended that the system library version of iconv() 142 be used rather than libiconv since there are incompatibilities 143 in the way codesets are named. 144 145 The UCB versions of the routines for reading directories are not 146 usable (the struct definitions are incompatible with the ones 147 assumed by zsh). The symptom of this is that globbed filenames in 148 the compiled version of zsh will be missing the first two letters. 149 To avoid this, make sure you compile zsh without any reference 150 to /usr/ucblib in your LD_LIBRARY_PATH. You can easily do this 151 by just unsetting LD_LIBRARY_PATH before building zsh. 152 153 Problems were once reported using --enable-largefile (the default) to 154 enable large file system and integer support on Solaris 2 with gcc 155 before 2.95.2. Recent versions of gcc appear to be unproblematic. 156 157Other machines 158-------------- 159 160Zsh has previously been compiled on the following machines, but the 161developers do not have direct access to them and the reports may be out 162of date. Some of these OS's are now very long in the tooth. We would 163be glad to receive any reports of success or failure on these OS's --- 164and, of course, any others not mentioned in this file. 165 166Apple/NeXT OpenStep 4.2 for i386. 167 Reported to work at least with gcc 2.8.1 and gawk 2.15 patchlevel 168 6, but not with the bundled cc 2.7.2.1 and awk. 169 170Cray: Unicos (C90 and T90) 171 Should build `out-of-the-box'. 172 173Data General: DG/UX 5.4R3.10 MU01 (various AViiONs) 174 Should build `out-of-the-box'. 175 176DEC: Ultrix (Alpha or DECstation) 177DEC: Mach 3.0 (DECstation 5000/25) 178DEC: OSF/1 1.2, 1.3, 2.0, 3.x, DEC Unix 4.x (Alpha) 179 180HP/Compaq: Tru64 4.x, 5.x 181 182Next: NextStep 3.* 183 Should build `out-of-the-box', but the zsh malloc routines are 184 not recommended. 185 186SCO: UnixWare 2.1.3 187 Builds `out-of-the-box'. 188 189SGI: IRIX 6.2, 6.3, 6.5 190 191SIEMENS: SINIX 192 193SIEMENS: Reliant UNIX 194 195Sun: SunOS 4.1.x 196