(1 Oct 2015) CIAO 4.7 does not work with Apple's OS X 10.11: El Capitan. While some individual tools and applications may work, many of the Python and Shell based applications and contributed scripts do not.
(20 Oct 2015) ChIPS in CIAO 4.7 is incompatible with XQuartz 2.7.8. Users must use version 2.7.7 or earlier.
CIAO 4.7 will be the last CIAO release that will be available for 32bit Linux and OSX 10.6.8/10.7.
Users are encouraged plan ahead for 2015 if still using any of these operating systems.
Some older versions of 64bit Linux can only run the 32bit binaries. This includes CentOS 5. These users will need to upgrade to be able to use the next version of CIAO.
CIAO 4.7 is available as precompiled binaries for the following platforms:
- Linux 32 bit and 64 bit
The Linux64 builds are done on a CentOS 6.5 machine and have been fully tested on CentOS 6 and Fedora Core 16. The Linux64 build will not work on some older Linux operating systems, including CentOS 5.
Users have reported successfully installing CIAO on Debian based Linux distributions: Ubuntu and Linux Mint, on Fedora based distributions: Red Hat, CentOS, and Scientific Linux, as well as OpenSUSE and Mageia.
CIAO 4.7 does not run on standard installations of:
- RHEL version 4 or lower
- Slackware Linux (missing SELinux system library)
The Linux (32bit) builds are done on a CentOS 5.10 machine. This is the only build available for CentOS 5 and older 32-bit and 64-bit Linux operating systems.
- Mac OS X, 64 bit
There are two OSX binary releases.
The osx64 build is built on OSX 10.6.8 (Snow Leopard) and is compatible with OSX 10.7 (Lion).
The osxml64 build is built on OSX 10.8 (Mountain Lion) and is compatible with OSX 10.9 (Mavericks) and OSX 10.10 (Yosemite)
CIAO 4.7 does not run on:
- Mac OS X 10.5 or lower
- Mac PowerPC
- Mac 32bit
Installing 32-bit CIAO on 64-bit Machines
The 64-bit installations of CIAO are recommended for Linux platforms with that architecture.
It is possible to install the 32-bit CIAO on these platforms as well, but the basic 32-bit libraries must be installed. The 32-bit libraries are not packaged with CIAO; the user is responsible for installing them via the package manager (e.g. yum, fink).
The names may differ slightly but here are the known packages:
- GL libs (Open GL or Mesa)
- C libraries
- C++ libraries
Doing an ldd on our executables and libraries yields the following list of system libraries:. They should live in either /lib or /usr/lib:
libncurses.so.5 libXt.so.6 libgnutls.so.13 libm.so.6 libSM.so.6 libkrb5support.so.0 libdl.so.2 libICE.so.6 libkeyutils.so.1 libstdc++.so.6 libXrandr.so.2 libresolv.so.2 libgcc_s.so.1 libXrender.so.1 libgcrypt.so.11 libc.so.6 libXinerama.so.1 libgpg-error.so.0 ld-linux.so.2 libXau.so.6 libnsl.so.1 libX11.so.6 libXdmcp.so.6 libsepol.so.1 libGLU.so.1 libdl.so.2 libz.so.1 libGL.so.1 libselinux.so.1 librt.so.1 libXmu.so.6 libcrypt.so.1 libpthread.so.0
The CXC's commitment to support a platform - i.e. a version of an operating system - means that we undertake to fix bugs on that system. This requires that we are able to compile CIAO from source on each platform, which is a much greater commitment than simply providing a compatible binary. Additionally, it is typically necessary to support three versions of each operating system: former, current and new.
When we support a system:
- We test every tool on every platform via a large number of regression tests and scripts; this requires a greater amount of time when the number of systems increases.
- We have to have current machines running each of these systems.
- We make a tarball and install it on each system; this process is never problem-free, and takes manpower and time.
As a result, we are not able to support a larger number of systems than we currently do. We gather information from users on what platforms they are running (or want to use) in order to prevent the overextension of our resources.