I have changed an application that used the older 32bit RFA 6.5 C++ on RedHat Linux to use the current version 7.7. This resulted in a problem with libRFA_Adapter.so trying to open libTibMsg.so from an absolute path outside the RFA installation. The library file does not have an rpath set but it contains the full path as a string:
QUESTION:Can I prevent the RFA_Adapter from trying to open the TibMsg library from that path by configuration or is this behaviour hard coded? In my view, the latter case would mean that Refinitiv should provide a new version without this behaviour. Would you be able to do so?
My current workaround is to create the full path and link the library from the RFA installation directory. I would very much like to avoid this in a later production installation.
Thank you very much in advance for any suggestions.
You are correct. It could be a problem in RFA 7.7.0.L1.
[root@localhost RHEL6_32_GCC444]# ldd libRFA_Adapter.so.7 linux-gate.so.1 => (0x00824000) libRFA_Config.so => not found libRFA_Logger.so => not found libRFA_Common.so => not found libRFA_Connections.so => not found libRFA_Connections_MD.so => not found libTibMsg.so => ./libTibMsg.so (0x0072b000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00893000) libm.so.6 => /lib/libm.so.6 (0x0046d000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00386000) libc.so.6 => /lib/libc.so.6 (0x00110000) /lib/ld-linux.so.2 (0x009b6000)
[root@localhost RHEL6_32_GCC444]# ldd libRFA_Adapter.so.7 linux-gate.so.1 => (0x00a55000) libRFA_Config.so => ./libRFA_Config.so (0x00110000) libRFA_Logger.so => ./libRFA_Logger.so (0x00f4d000) libRFA_Common.so => ./libRFA_Common.so (0x0015d000) libRFA_Connections.so => ./libRFA_Connections.so (0x0052f000) libRFA_Connections_MD.so => ./libRFA_Connections_MD.so (0x003a1000) libTibMsg.so => ./libTibMsg.so (0x00590000) /local/jenkins/workspace/RFACPP_762_Core/OS/RH6-32/tapi/prod/x86_Linux_6X/gnu44-o/lib/lib_so/libTibMsg.so => not found libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00721000) libm.so.6 => /lib/libm.so.6 (0x00aea000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x001b2000) libc.so.6 => /lib/libc.so.6 (0x001d0000) librt.so.1 => /lib/librt.so.1 (0x00360000) /lib/ld-linux.so.2 (0x009b6000) libpthread.so.0 => /lib/libpthread.so.0 (0x00369000)
Please submit this case to the RDC support team via Contact Premium Support to verify and fix this issue.