MacOS binaries are provided. The Debian workaround is not needed anymore (see bug 5481). Solaris 10 may need some environment variables set to build with vendor-provided openssl (see http://dev.globus.org/wiki/C_Security:_Vendor_OpenSSL#Known_Issues_and_Workarounds)

CentOS has a GSSAPI with compression enabled, which will cause GRAM2 error code 10 if you use the gatekeeper/jobmanager. Please apply the advisory from http://www.globus.org/toolkit/advisories.html?version=4.2#globus_gssapi_gsi-5.4 after building. This fix is already included in GT4.2.1.

Some kernel/libc combinations trigger a threading problem. See bug #2194. The workaround is to set LD_ASSUME_KERNEL=2.2.5 in your environment.

Fedora Core 2 and later ship with a broken ant. Install your own ant from http://ant.apache.org and either remove the ant RPM or edit /etc/ant.conf, setting ANT_HOME to your own ant installation.

No known issues.

4.2.0 has not been tested on HP-UX.

For HP-UX/IA64 and for additional details about GT4 on HP-UX/PA-RISC, please consult the HP GT4 support page.

Supported flavors are vendorcc32dbg/vendorcc32 and vendorcc64dbg/vendorcc64 using the Visual Age compilers (xlc). No gcc flavors are supported. Specify a flavor using --with-flavor=flavor.

GNU sed, tar, and make are required before the IBM ones in the PATH.

The toolkit has been tested on AIX 5.2 with:

RHEL5 has upgraded to openssl0.9.8. Our RHAS3/4 binaries are built using openssl0.9.7. You will either need to build from source on RHEL5+, or install the older RHEL4 openssl 0.9.7 RPMs.

When building from source on a Red Hat Enterprise line version 3 or 4 based OS, GPT might have a problem retrieving exit codes from subshells. You might see errors which says they were both successful and failed:

 BUILD SUCCESSFUL Total time: 11 seconds ERROR: Build has failed make: ***
            [globus_wsrf_servicegroup] Error 10

The workaround is to configure with --with-buildopts="-verbose"

Some extra environment variables are required for building MPI flavors. For the Intel compiler:

 export CC=icc export CFLAGS=-no-gcc export CXX=icpc export CXXFLAGS=-no-gcc export
            LDFLAGS=-lmpi

For the GNU compiler:

 export CC=gcc export CXX=g++ export LDFLAGS=-lmpi

In both cases, configure with --with-flavor=mpicc64

Supported flavors are gcc32, gcc64, vendorcc32 and vendorcc64. The dbg flavors should work as well. For gcc64, a gcc built to target 64 bit object files is required. The gcc32dbg flavor will be used by default. Specify other flavors using --with-flavor=flavor.

For Solaris 10, you may need to use an updated GNU binutils, or the provided Sun /usr/ccs/bin/ld to link. See binutils bug 1031 for details on Solaris 10 symbol versioning errors.

The toolkit has been tested on Solaris 10 with:

No known issues.

Specify --with-flavor=vendorcc64 on the configure line. GNU tar, GNU sed, and GNU make are required on the PATH.

The toolkit has been tested on Tru64 UNIX (V5.1A and V5.1B) with:

For additional details about GT4 on Tru64 Unix, please consult the HP GT4 support page.

Only Java-only components will build. Please choose the Java WS Core-only download and follow the instructions in the Java WS Core Admin Guide.