Hi,
The `run_cmd` function you see in the trace is a fairly thin wrapper over an `exec` call, so my guess would be that the detection for which version of the tools to use is failing in some way.
Could you provide the output from this command?
$ getconf LONG_BIT
This is how Globus Connect Personal does platform detection. If it fails, I would expect RELAYTOOL to be something malformed, and for this later command to fail.
If you're feeling adventurous, you could also modify the setup.py script to add some debug printing to look directly at the value for RELAYTOOL.
e.g. near the top of setup.py, when that value is set, just add
print("RELAYTOOL=" + RELAYTOOL)
(Yes, this definitely should be doable in a cleaner way. But this way will work for today.)
A couple of additional notes on this, which might help:
Just to be clear, Globus Toolkit and Globus Connect Personal are very different.
If you're looking to create a grid compute environment, Globus Connect Personal may not be appropriate to your case.
> running the globusconnectclient.
Do you mean "globusconnectpersonal" or "globusconnect" (which are just aliases for one another) ?
I'm not familiar with a command named "globusconnectclient", though it's possible I've forgotten a past name for these.
Best,
-Stephen