Linux

Unfortunately  it is not possible to have a single Linux release. The new version of the libc shared library (libc.so.6) is incompatible with earlier versions. As  Texpress and TexAPI programs depend on libc it is necessary to distinguish between programs compiled for libc version 6 and those compiled for earlier versions of the library. Typically Linux vendors have shipped version 6 libraries with the Linux kernel 2.2 and above and version 5 libraries with the kernel 2.0 or earlier. For example, Red Hat 5.2 and earlier comes with a 2.0 kernel and version 5 libc libraries while Red Hat 6.0 and above has shipped a version 2.2 kernel and libc version 6.

Confused? We were too. The best way to determine your libc version is to run the ldd command on a standard program and check what libc dependency exists. For example, on our Red Hat 6.0 system we get the following:

$ ldd /bin/sh
libtermcap.so.2 => /lib/libtermcap.so.2 (0x40017000)
libc.so.6 => /lib/libc.so.6 (0x4001b000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

Obviously libc version 6. On our Slackware 3 system we get the following:

$ ldd /bin/sh
libtermcap.so.2 => /lib/libtermcap.so.2.0.8
libc.so.5 => /lib/libc.so.5.3.12

Looks like libc version 5.

SCO OpenServer 5 (Unixware-compatible)

These binaries have been compiled on a machine running SCO OpenServer 5 using the SCO UDK (Unixware Development Kit). This development kit creates binaries which should run on both SCO OpenServer platforms and Unixware platforms. We have not tested the Unixware compatibility, however. More information on the SCO OpenServer and Unixware  is available from SCO. Details on the SCO UDK are also available.

UWIN (Windows NT/2000)

UWIN is a Unix-like toolkit for Windows NT/2000. To use this release of KE Texpress you need the UWIN base toolkit. More information about UWIN is available from AT&T Research Labs.