• pyGlobus homepage
• Download GTG Software

• Bugzilla: report a bug
• GTG
• DSD
• DOE SG
• LBNL
• NERSC
• CS Division

The build process of globus tends to change from release to release. The important thing is to realize that you need some the globus C libraries. As of the globus-3.2 release these bundles are called globus-data-management-sdk-3.2-src_bundle.tar.gz and globus-resource-management-sdk-3.2-src_bundle.tar.gz. If you are using an earlier release you just need to build data-management and resource-management sdk bundles that came with that release. You can find these in the Pre-WS bundles section on the download page at www.globus.org. You must build these with a threaded flavor (ie: gcc32dbgpthr). We also recommend installing the resource management client bundle because that will give you the client programs grid-proxy-init, which you will need, and globusrun.

To install pyGlobus you must have your GLOBUS_LOCATION and GPT_LOCATION environment variables set to a valid globus install and gpt install directory. The most common case is that these are installed in the same directory. pyGlobus uses distutils so the installation process is the same for packages that use distutils.
%python setup.py build --run-swig

To verify the pyGlobus installation you can run the unittests that come packaged with pyGlobus. Many of the unittests rely on site specfic configuration variables. So many of the unittests will fail unless you edit the config.txt file that resides in the test directory.

cvs -d :pserver:anonymous@bosshog.lbl.gov:/home/portnoy/u5/repository login

hit enter when prompted for the password

cvs -d :pserver:anonymous@bosshog.lbl.gov:/home/portnoy/u5/repository co pyGlobus

You need to install swig version 1.3.24 or later to build the *_wrap.c files. The swig that comes with redhat won't work.You can get it here www.swig.org. When you build pyGlobus you need to pass the --run-swig option to setup.py.
Like this:
%python setup.py build --run-swig

If you wish to use the myProxy and rlsClient functionality you need to install those packages in your globus installation. The rlsClient package provides an API for using a replica location service. In a sentence it is useful for managing large files physically and logically over several machines. Here is a link to the RLS homepage . The myProxy package provides allows you to store your user proxy for a long periods of time on a dedicated proxy server. Here is a link to the myProxy homepage . These packages should be built with a threaded flavor if you want to use the pyGlobus myProxy or rlsClient modules.

For each module we have to make a globus-makefile-header call. This is the takes the more time than anything else. If you are doing development we would recommend using the --make-gmfh-cache and --use-gmfh-cache options.
Like this:
%python setup.py build --make-gmfh-cache
And on subsequent builds
%python setup.py build --use-gmfh-cache
What this does is create a cache of the globus-makefile-header output, and then on subsequent builds it uses this cache, which signifcantly reduces the time to build pyGlobus.

Send you question to python-discuss@globus.org. We will answer your question and after deeming it FAQworthy, put it on this page.