Hi Jeremy,
> The RPM finally built this time with a few edits to the SPEC file.
> However, I don't think it compiled the SOAP python module. When running
> VenueClient.py for the first time I get:
> When I look in the build directory and do a grep for SOAP, I see:
>
> buf:~/AG-build/build/dist-20050913_081757 # find . |grep SOAP
> ./lib64/python2.4/site-packages/pyGlobus/GSISOAP.py
> ./lib64/python2.4/site-packages/AccessGrid/hosting/SOAPpy
> ./lib64/python2.4/site-packages/AccessGrid/hosting/SOAPpy/Client.py
> ./lib64/python2.4/site-packages/AccessGrid/hosting/SOAPpy/Tools.py
> ./lib64/python2.4/site-packages/AccessGrid/hosting/SOAPpy/Server.py
> ./lib64/python2.4/site-packages/AccessGrid/hosting/SOAPpy/__init__.py
> ./lib64/python2.4/site-packages/AccessGrid/hosting/SOAPInterface.py
>
> What else can I check for?
BuildSnapshot.py calls BuildPythonModules.py which builds SOAPpy-0.11.4 with
the equivalent of the following sequence of events happening, you could try
to reproduce it on the command-line to see if there is a problem with
building SOAPpy:
cd SOAPpy-0.11.4
python setup.py clean --all
python setup.py build
python setup.py install --prefix=../dist-20050914/lib/python2.4/site-packages
--no-compile
Note: the files are put in a 'lib' dir instead of a 'lib64' dir, so the
AccessGrid RPM spec file recitifies it latter by doing the following:
mv lib/python%{pyver}/site-packages/* usr/lib64/python%{pyver}/site-packages
Also make sure you have all the gpt, globus-accessgrid, wxpython/wxGTK x86_64
RPMs installed and not just the i386/i586 versions.
The x86-64 mods in the AccessGrid.spec.in file were the ones I used for x86-64
Fedora Core 3. I no longer have access to any PC running x86-64 linux at the
moment.
Cheers,
Doug
