[ECOS] ecosconfig on linux problem

[ECOS] ecosconfig on linux problem

[Henri]

a new build of ecosconfig from yesterday's cvs builds without errors but does 
not execute .  Build is on a redhat 7.2 linux 

build directory was under ......../ecos_download_021028/ecos/host

any hint of what could be done to get this program working  is appreciated 

thanks 

Henri 



[henri@localhost henri]$ ecosconfig --help
ecosconfig: error while loading shared libraries: libstdc++.so.5: cannot open 
shared object file: No such file or directory

the installation sets up a link from libstdc++.so.5 to  libstdc++.so.5.0.0
it would appear that ecosconfig cannot accept the link . 


+.so.5.0.0
lrwxrwxrwx    1 root     root           18 Oct 28 15:15 libstdc++.so.5 -> 
libstdc++.so.5.0.0
-rwxr-xr-x    1 root     root      5585580 Oct 28 15:15 libstdc++.so.5.0.0


--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

Re: [ECOS] ecosconfig on linux problem

[Bart Veer]

>>>>> "Henri" == Henri  <henri@broadbandnetdevices.com> writes:

    Henri> a new build of ecosconfig from yesterday's cvs builds
    Henri> without errors but does not execute . Build is on a redhat
    Henri> 7.2 linux

    Henri> build directory was under ......../ecos_download_021028/ecos/host

    Henri> any hint of what could be done to get this program working
    Henri> is appreciated

    Henri> [henri@localhost henri]$ ecosconfig --help
    Henri> ecosconfig: error while loading shared libraries: libstdc++.so.5: 
    Henri> cannot open shared object file: No such file or directory

This is not a problem with ecosconfig, but with the system generally.
I suspect you would get the same error for any C++ program you build.
Unfortunately I do not know exactly what is causing the problem - I
suspect that you are also using a g++ and linker you have built
yourself, and somehow that is not or no longer installed properly.
If so, it would be worth trying to build with the system's
/usr/bin/g++ and see if that makes any difference.

Otherwise it is necessary to figure out what is going wrong with
shared libraries generally. You can use the ldd utility to find out
exactly what shared libraries are being used. For a current ecosconfig
build I see

    /lib/libsafe.so.1.3 => /lib/libsafe.so.1.3 (0x40014000)
    libtcl.so.0 => /usr/lib/libtcl.so.0 (0x40031000)
    libdl.so.2 => /lib/libdl.so.2 (0x400b1000)
    libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x400b4000)
    libm.so.6 => /lib/i686/libm.so.6 (0x400f7000)
    libc.so.6 => /lib/i686/libc.so.6 (0x42000000)
    /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

So on this machine ecosconfig is linked with libstdc++-libc6.2-2.so.3
(or any later version of the library that is backwards compatible),
and the dynamic linker has found a suitable library in /usr/lib.
Library search information typically comes from the file
/etc/ld.so.conf

For more information, see the man pages for ldconfig, ldd, and ld.so

Bart

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss