[ROOT] Problems with shared libraries in rootd authentication

From: Birger Koblitz (Birger.Koblitz@cern.ch)
Date: Mon Apr 26 2004 - 15:09:37 MEST


I am looking into PROOF for the ARDA project and did some tests with the 
rootd, first. I ran into the following problem:
I use the root 4.00.03 installation at 
/afs/cern.ch/sw/root/v4.00.03/rh73_gcc32/root and have started up the 
rootd successfully. Now, when I try to authenticate via ssh, I get

/afs/cern.ch/sw/root/v4.00.03/rh73_gcc32/root/bin/ssh2rpd: error while 
loading shared libraries: libgcc_s.so.1: cannot open shared object file: 
No such file or directory

It seems my LD_LIBRARY_PATH settings are not correctly taken into account. 
Looking at 
ldd /afs/cern.ch/sw/root/v4.00.03/rh73_gcc32/root/bin/ssh2rpd
        libdl.so.2 => /lib/libdl.so.2 (0x4002a000)
        libstdc++.so.5 => /usr/local/gcc-alt-3.2.3/lib/libstdc++.so.5 
        libm.so.6 => /lib/i686/libm.so.6 (0x400df000)
        libgcc_s.so.1 => /usr/local/gcc-alt-3.2.3/lib/libgcc_s.so.1 
        libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

suggests problems with the gcc3.2 libraries. As root on that machine I 
fixed this problem easily by links of libstdc++.so.5 and lib/libgcc_s.so.1 
into /lib. My question:

Within the Grid-Framework it will be necessary that the users run 
individualized versions of root on the machines depending on their library 
paths. They cannot depend on the superuser to solve their problems. Did I 
overlook anything, or is this currently impossible?


Birger Koblitz                  +41 22 767-3318
CERN IT                         2-1-046

This archive was generated by hypermail 2b29 : Sun Jan 02 2005 - 05:50:07 MET