Hello Team,

Just after a nice meeting with Sanket, I updated our local repository to check what's new in the Toolbox and found a problem with the new sudo_ids package.
I tried to use the 64bit version and got following error:

:/#sudo_64 -VCould not load program sudo:        Dependent module /usr/lib/libibmldap.a could not be loaded.Could not load module /usr/lib/libibmldap.a.System error: Exec format error

It seems sudo_64 uses the wrong 'libibmldap.a'. I would expect the correct lib to be '/usr/lib/lib64/libibmldap.a'.
This is a link to '/opt/IBM/ldap/V6.4/lib64/libidsldap.a' set via the 'idslink -i -g -l 64 -f ' command.

best regards,
Joerg

Hello Team,

Just after a nice meeting with Sanket, I updated our local repository to check what's new in the Toolbox and found a problem with the new sudo_ids package.
I tried to use the 64bit version and got following error:

:/#sudo_64 -VCould not load program sudo:        Dependent module /usr/lib/libibmldap.a could not be loaded.Could not load module /usr/lib/libibmldap.a.System error: Exec format error

It seems sudo_64 uses the wrong 'libibmldap.a'. I would expect the correct lib to be '/usr/lib/lib64/libibmldap.a'.
This is a link to '/opt/IBM/ldap/V6.4/lib64/libidsldap.a' set via the 'idslink -i -g -l 64 -f ' command.

best regards,
Joerg

Hello Team,

Just after a nice meeting with Sanket, I updated our local repository to check what's new in the Toolbox and found a problem with the new sudo_ids package.
I tried to use the 64bit version and got following error:

:/#sudo_64 -VCould not load program sudo:        Dependent module /usr/lib/libibmldap.a could not be loaded.Could not load module /usr/lib/libibmldap.a.System error: Exec format error

It seems sudo_64 uses the wrong 'libibmldap.a'. I would expect the correct lib to be '/usr/lib/lib64/libibmldap.a'.
This is a link to '/opt/IBM/ldap/V6.4/lib64/libidsldap.a' set via the 'idslink -i -g -l 64 -f ' command.

best regards,
Joerg

Hello Team,

Just after a nice meeting with Sanket, I updated our local repository to check what's new in the Toolbox and found a problem with the new sudo_ids package.
I tried to use the 64bit version and got following error:

:/#sudo_64 -VCould not load program sudo:        Dependent module /usr/lib/libibmldap.a could not be loaded.Could not load module /usr/lib/libibmldap.a.System error: Exec format error

It seems sudo_64 uses the wrong 'libibmldap.a'. I would expect the correct lib to be '/usr/lib/lib64/libibmldap.a'.
This is a link to '/opt/IBM/ldap/V6.4/lib64/libidsldap.a' set via the 'idslink -i -g -l 64 -f ' command.

best regards,
Joerg

:/root#echo $LIBPATH

there is no output...

@Ayappan P : The dump output shows the correct path for Ldap Version 6.3 (/opt/IBM/ldap/V6.3/lib64), but we are using Ldap Version 6.4.
Therefore after the installation of IBM LDAP "isdlink" creates sym. links for the 32bit lib in "/usr/lib/" and for the lib 64bit in "/usr/lib/lib64/", but your dump output shows "/usr/lib64"  

:/root#ls -la /usr/lib/libibmldap.alrwxrwxrwx-  1 root  system   35 Jun 9 09:58 /usr/lib/libibmldap.a -> /opt/IBM/ldap/V6.4/lib/libidsldap.a:/root#ls -la /usr/lib/lib64/libibmldap.alrwxrwxrwx-  1 root  system    37 Jun 9 09:58 /usr/lib/lib64/libibmldap.a -> /opt/IBM/ldap/V6.4/lib64/libidsldap.a

Of course I could manually set a link for the 64bit libibmldap.a to /usr/lib64, but I think it should work out of the box. Maybe there was a change in setting the links to the libs wirth idslink in LDAP Version 6.4... maybe you could check this (/opt/IBM/ldap/V6.4/bin/idslink -i -g -l 64 -f) in your system with Version 6.3. Maybe that's the problem...

Please, what is your suggestion?

Best regards,

Joerg

Hello Team,

Just after a nice meeting with Sanket, I updated our local repository to check what's new in the Toolbox and found a problem with the new sudo_ids package.
I tried to use the 64bit version and got following error:

:/#sudo_64 -VCould not load program sudo:        Dependent module /usr/lib/libibmldap.a could not be loaded.Could not load module /usr/lib/libibmldap.a.System error: Exec format error

It seems sudo_64 uses the wrong 'libibmldap.a'. I would expect the correct lib to be '/usr/lib/lib64/libibmldap.a'.
This is a link to '/opt/IBM/ldap/V6.4/lib64/libidsldap.a' set via the 'idslink -i -g -l 64 -f ' command.

best regards,
Joerg

:/root#echo $LIBPATH

there is no output...

@Ayappan P : The dump output shows the correct path for Ldap Version 6.3 (/opt/IBM/ldap/V6.3/lib64), but we are using Ldap Version 6.4.
Therefore after the installation of IBM LDAP "isdlink" creates sym. links for the 32bit lib in "/usr/lib/" and for the lib 64bit in "/usr/lib/lib64/", but your dump output shows "/usr/lib64"  

:/root#ls -la /usr/lib/libibmldap.alrwxrwxrwx-  1 root  system   35 Jun 9 09:58 /usr/lib/libibmldap.a -> /opt/IBM/ldap/V6.4/lib/libidsldap.a:/root#ls -la /usr/lib/lib64/libibmldap.alrwxrwxrwx-  1 root  system    37 Jun 9 09:58 /usr/lib/lib64/libibmldap.a -> /opt/IBM/ldap/V6.4/lib64/libidsldap.a

Of course I could manually set a link for the 64bit libibmldap.a to /usr/lib64, but I think it should work out of the box. Maybe there was a change in setting the links to the libs wirth idslink in LDAP Version 6.4... maybe you could check this (/opt/IBM/ldap/V6.4/bin/idslink -i -g -l 64 -f) in your system with Version 6.3. Maybe that's the problem...

Please, what is your suggestion?

Best regards,

Joerg

Hello Team,

Just after a nice meeting with Sanket, I updated our local repository to check what's new in the Toolbox and found a problem with the new sudo_ids package.
I tried to use the 64bit version and got following error:

:/#sudo_64 -VCould not load program sudo:        Dependent module /usr/lib/libibmldap.a could not be loaded.Could not load module /usr/lib/libibmldap.a.System error: Exec format error

It seems sudo_64 uses the wrong 'libibmldap.a'. I would expect the correct lib to be '/usr/lib/lib64/libibmldap.a'.
This is a link to '/opt/IBM/ldap/V6.4/lib64/libidsldap.a' set via the 'idslink -i -g -l 64 -f ' command.

best regards,
Joerg

:/root#echo $LIBPATH

there is no output...

@Ayappan P : The dump output shows the correct path for Ldap Version 6.3 (/opt/IBM/ldap/V6.3/lib64), but we are using Ldap Version 6.4.
Therefore after the installation of IBM LDAP "isdlink" creates sym. links for the 32bit lib in "/usr/lib/" and for the lib 64bit in "/usr/lib/lib64/", but your dump output shows "/usr/lib64"  

:/root#ls -la /usr/lib/libibmldap.alrwxrwxrwx-  1 root  system   35 Jun 9 09:58 /usr/lib/libibmldap.a -> /opt/IBM/ldap/V6.4/lib/libidsldap.a:/root#ls -la /usr/lib/lib64/libibmldap.alrwxrwxrwx-  1 root  system    37 Jun 9 09:58 /usr/lib/lib64/libibmldap.a -> /opt/IBM/ldap/V6.4/lib64/libidsldap.a

Of course I could manually set a link for the 64bit libibmldap.a to /usr/lib64, but I think it should work out of the box. Maybe there was a change in setting the links to the libs wirth idslink in LDAP Version 6.4... maybe you could check this (/opt/IBM/ldap/V6.4/bin/idslink -i -g -l 64 -f) in your system with Version 6.3. Maybe that's the problem...

Please, what is your suggestion?

Best regards,

Joerg

Hello Team,

Just after a nice meeting with Sanket, I updated our local repository to check what's new in the Toolbox and found a problem with the new sudo_ids package.
I tried to use the 64bit version and got following error:

:/#sudo_64 -VCould not load program sudo:        Dependent module /usr/lib/libibmldap.a could not be loaded.Could not load module /usr/lib/libibmldap.a.System error: Exec format error

It seems sudo_64 uses the wrong 'libibmldap.a'. I would expect the correct lib to be '/usr/lib/lib64/libibmldap.a'.
This is a link to '/opt/IBM/ldap/V6.4/lib64/libidsldap.a' set via the 'idslink -i -g -l 64 -f ' command.

best regards,
Joerg