GT 2.4: Platform Specific Build and Installation Issues

Software Build Issues: TRU64 / alpha / vendorcc64 / GT 2.0

Operating System CPU
Arch 		Flavor
Used 		Globus
Version
Name Version
Tru64 5.1 alpha vendorcc64 2.0

Notes:

    The Globus Toolkit 2.0 source bundles have been built and tested on Compaq Alpha systems running Tru64TM UNIX (V5.0A, V5.1, V5.1A and V5.1B). While the Globus Toolkit installation instructions apply to Tru64 UNIX, there are several additional requirements that must be met; these are documented below.

    • The following GNU software packages must be installed:
      • make (which requires m4 and autoconf), and
      • tar.
      The directory where these tools are installed must precede /usr/bin in the shell $PATH variable.
    • Depending on which bundles are built, the Tru64 UNIX V5.0A and V5.1 linker may fail to create shared libraries due to multiply defined symbols. This linker problem was fixed in Patch Kit 3 (BL17) and does not affect V5.1A (and beyond). Known work-arounds include using the linker -noso and -so_archive flags to choose archive libraries over their shared counterparts, or moving the offending shared libraries to a temporary directory during the link phase.
    • The $CC environment variable should be set to /usr/bin/cc. This will ensure that the Tru64 UNIX C compiler will be selected over any other installed compilers (e.g., gcc).
    • Use 64-bit flavored builds on Tru64 UNIX (e.g., vendorcc64); the 32-bit flavors will not work.
    • The globus-postinstall.sh script displays the message "-: No such file or directory" because the Tru64 UNIX Bourne shell does not support "cd -" (return to previous directory). While harmless in this context, using Tru64 UNIX V5.1 and beyond, the script can be run under the Korn shell (ksh) to eliminate the message.
    • Globus services spawned from inetd require that $LD_LIBRARY_PATH be initialized. One way to accomplish this is to install the following script (owner root, mode 555) as $GLOBUS_LOCATION/sbin/inetd-wrapper: 
      #! /bin/sh
GLOBUS_LOCATION=/globus/obj
LD_LIBRARY_PATH=${GLOBUS_LOCATION}/lib
export LD_LIBRARY_PATH
exec ${1+"$@"}
      Then, use the script to launch the services. For example, given $GLOBUS_LOCATION as defined above, the globus-gatekeeper line in /etc/inetd.conf should read:
      globus-gatekeeper stream tcp nowait root /globus/obj/sbin/inetd-wrapper inetd-wrapper /globus/obj/sbin/globus-gatekeeper -conf /globus/obj/etc/globus-gatekeeper.conf
      Note that, allowing root to execute scripts or applications owned by another user effectively equates that user to the superuser. Also, similar security issues are raised if any component of the path to an executable is not owned by root.
    • While the Tru64 UNIX MDS information providers did not make it into the Globus Toolkit 2.0 release, prototype Tru64 providers can be installed by running this shell script anytime after installing the IS Server bundle. Tru64 UNIX MDS information providers will be available in MDS 2.2.

Contributed by:  

    Compaq Computer Corporation

[back to build page]