Workarounds: Native launcher dependency-related problems in Source Control Command Line Interface for Rational Team Concert 4.0.3
Build basis: Rational Team Concert 4.0.3
The following known problems are related to the native launcher in the Source Control Command Line Interface for Rational Team Concert 4.0.3.
Workarounds
The following problems in this release have workarounds:
- Error while running lscm on Microsoft Windows XP SP2 (and other older Windows releases)
- Error while running lscm on 64-bit Linux (also, possible on other supported 64-bit Unix) platforms
Workaround summary
Error while running lscm on Microsoft Windows XP SP2 (and other older Windows releases)
Author: Source Control Command Line Interface Team
Last updated: 28 May 2013
Problem
Executing lscm on Microsoft Windows XP SP2 (and other older Windows releases) fails with the following error:
The system cannot execute the specified program.
Sometimes, the same problem manifests itself as an application initialization error.
Reason: This error is thrown because the Visual C++ 2008 32-bit C and C++ runtimes are not available by default on older releases of Microsoft Windows.
Starting with the Rational Team Concert 4.0.3 release, we have included a native launcher (implemented in C++), which is a 32-bit application, and depends on Microsoft Visual C++ 2008 C and C++ 32-bit runtime libraries. This native launcher is invoked by the lscm script.
Workaround
There are two approaches to resolve this problem:
Approach 1: Install Microsoft Visual C++ 2008 redistributable package
Download and install the Microsoft Visual C++ 2008 redistributable package. It is available for download at http://www.microsoft.com/en-in/download/details.aspx?id=29.Approach 2: Setting the environment variable LSCM_USE_JAVA_FEC
Set the environment variable LSCM_USE_JAVA_FEC to any value, for example:
set LSCM_USE_JAVA_FEC=xyz.
Setting this environment variable makes the lscm script choose the Java launcher, instead of the the native launcher.
Related information
Workaround summary
Error while running lscm on 64-bit Linux (possible on other supported 64-bit Unix) platforms.
Author: Source Control Command Line Interface Team
Last updated: 28 May 2013
Problem
lscm fails to execute on 64-bit Linux (possible on other supported Unix) platforms with the error
fec: error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory.
Reason: This error is thrown because 32-bit standard C/C++ libraries are not available by default on on some 64-bit Linux (or other supported 64-bit UNIX) platforms.
Starting with the Rational Team Concert 4.0.3 release, we have included a native launcher (implemented in C++), which is a 32-bit application. This requires 32-bit versions of standard libraries to be available. The native launcher is invoked by the lscm script.
Workaround
There are two approaches to resolve this problem:
Approach 1: Install the required dependencies
Install the required dependent libraries. The dependencies are specific to your platform and are documented below.Approach 2: Setting the environment variable LSCM_USE_JAVA_FEC
Set the environment variable LSCM_USE_JAVA_FEC to any value, for example (on bash):
$ export LSCM_USE_JAVA_FEC=xyz
Setting this environment variable makes lscm script choose the Java launcher, instead of the the native launcher.
Related information
Platform-Specific Dependencies
- Linux-x86:
Compiler used: g++ 4.1.2
Dependencies:
RPM Package libstdc++-4.1.2.50.el5 (i386) (32-bit)
RPM Package glibc-2.5.58 (i686) (32-bit)
Dependency Dump:
linux-gate.so.1
libstdc++.so.6 => /usr/lib/libstdc++.so.6
libm.so.6 => /lib/libm.so.6
libgcc_s.so.1 => /lib/libgcc_s.so.1
libc.so.6 => /lib/libc.so.6
/lib/ld-linux.so.2
NOTE: Info on linux-gate: http://www.trilithium.com/johan/2005/08/linux-gate/
- Linux-PowerPC:
Compiler used: g++ 4.4.6
Dependencies:
RPM Package libstdc++-4.4.6.3.el6 (ppc) (32-bit)
RPM Package glibc-2.12.1.47.el6_2.9 (ppc) (32-bit)
Dependency Dump:
linux-vdso32.so.1
libstdc++.so.6 => /usr/lib/libstdc++.so.6
libm.so.6 => /lib/libm.so.6
libgcc_s.so.1 => /lib/libgcc_s.so.1
libc.so.6 => /lib/libc.so.6
/lib/ld.so.1
- Linux-System/z:
Compiler used: g++ 4.1.2
Dependencies:
RPM Package libstdc++-4.1.2.50.el5 (s390) (32-bit)
RPM Package glibc-2.5.81 (s390) (32-bit)
Dependency Dump:
libstdc++.so.6 => /usr/lib/libstdc++.so.6
libm.so.6 => /lib/libm.so.6
libgcc_s.so.1 => /lib/libgcc_s.so.1
libc.so.6 => /lib/libc.so.6
/lib/ld.so.1
- Solaris-SPARC:
Compiler used: g++ v3.4.3
Dependency Dump:
libsocket.so.1 => /lib/libsocket.so.1
libnsl.so.1 => /lib/libnsl.so.1
libstdc++.so.6 => /usr/sfw/lib/libstdc++.so.6
libm.so.2 => /lib/libm.so.2
libgcc_s.so.1 => /usr/sfw/lib/libgcc_s.so.1
libc.so.1 => /lib/libc.so.1
libmp.so.2 => /lib/libmp.so.2
libmd.so.1 => /lib/libmd.so.1
libscf.so.1 => /lib/libscf.so.1
libdoor.so.1 => /lib/libdoor.so.1
libuutil.so.1 => /lib/libuutil.so.1
libgen.so.1 => /lib/libgen.so.1
/platform/sun4v/lib/libc_psr.so.1
/platform/sun4v/lib/libmd_psr.so.1
NOTE: On Solaris, the native launcher is built using gcc and not
the native compiler. - Mac OS:
Compiler used: Apple clang version 4.1 (tags/Apple/clang-421.11.66)
Dependency Dump:
/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)
- AIX:
Compiler used: Visual Age Compiler Suite (IBM XL C/C++ for AIX, V11.1 (5724-X13) Version: 11.01.0000.0000)
Dependency Dump:
/usr/lib/libc.a(shr.o)
/usr/lib/libC.a(shr.o)
/usr/lib/libC.a(ansi_32.o)
/usr/lib/libiconv.a(shr4.o)
/unix
/usr/lib/libcrypt.a(shr.o)
/usr/lib/libC.a(shrcore.o)
/usr/lib/libC.a(ansicore_32.o)
Copyright © 2013 IBM Corporation