PROOF with globus under MacosX 64

Hi,

I encounter a problem when trying to connect to Proof (alice proof cluster) with globus authentication.

With root v5-21-01-alice I get the following output

XrdSec: dlopen(libXrdSecgsi.so, 2): Symbol not found: __ZN15XrdSysPrivGuardC1Ejj
Referenced from: /Users/kleinb/cern/root_v5-21-01-alice/root/lib/libXrdSecgsi.so
Expected in: dynamic lookup
opening shared library libXrdSecgsi.so
XrdSec: No authentication protocols are available.
080721 10:16:46 001 Proofx : XrdProofConn::Init: failure: unable to get protocol object.
(class TProof*)0x0

TGrid::Connect(), works fine though

I also tried with the root trunk: similar message:

XrdSec: dlopen(libXrdSecgsi.so, 2): Symbol not found: __ZN15XrdSysPrivGuardC1Ejj
Referenced from: /Users/kleinb/cern/root_v5-21-01_trunk/root/lib/libXrdSecgsi.so
Expected in: dynamic lookup
opening shared library libXrdSecgsi.so
XrdSec: No authentication protocols are available.
080721 11:07:19 001 Proofx-E: Conn::Authenticate: unable to get protocol object.
080721 11:07:19 001 Proofx-E: Conn::GetAccessToSrv: client could not login at [lxb6043.cern.ch:1093]
080721 11:07:19 001 Proofx-E: Conn::Connect: failure: unable to get protocol object.
080721 11:07:19 001 Proofx-E: XrdProofConn: XrdProofConn: severe error occurred while opening a connection to server [lxb6043.cern.ch:1093]
(class TProof*)0x0

When I load a library which contains the undefined symbol (there are more than one …) I get a seg-fault

root [0] gSystem->Load(“libXrdSeckrb5.so”);
Reading symbols for shared libraries … done
root [1] TProof::Open(“lxb6043”)
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
0x0000000102ee210e in XrdCryptosslX509ParseFile ()

Any Idea how to fix this is welcome…

Christian

PS: My config option:

ALIEN_ROOT=/opt/alien/
./configure macosx64
–with-f77=gfortran
–with-pythia6-uscore=SINGLE
–enable-globus
–with-globus-incdir=${ALIEN_ROOT}/globus/include
–with-globus-libdir=${ALIEN_ROOT}/globus/lib
–enable-alien --with-alien-incdir=${ALIEN_ROOT}/api/include
–with-alien-libdir=${ALIEN_ROOT}/api/lib

and GLOBUS_LOCATION is set too
BTW. in the configure script the includes are hard-wired to

  • searchincdir="$globusincdir/gcc32 $globusincdir/gcc32dbg \
  •              $globusincdir/gcc32pthr $globusincdir/gcc32dbgpthr"
    

alien_installer puts it under gcc64, so I changed it for me to

  • searchincdir="$globusincdir/gcc64 $globusincdir/gcc64dbg \
  •              $globusincdir/gcc64pthr $globusincdir/gcc64dbgpthr"
    

this has no effect on the above messages.

For those interested, this is being followed on a different thread (on Savannah, see http://savannah.cern.ch/bugs/?39111).
The current status is that we found some problems which are being fixed into the trunk.
But there is still something preventing Christian to succeed, so the case is not yet closed.

Gerri Ganis