Skip to main content
November 8, 2006
Question

FMS 2 on Fedora Core 5

  • November 8, 2006
  • 1 reply
  • 578 views
Hi All,
I am tryiong to install FMS 2 on FC5
When I do a ./installFMS
I get the following error

./fmsini: error while loading shared libraries: libstdc++.so.5: cannot open shar ed object file: No such file or directory

Any pointers on how to resolve this issue would be really helpful.
Thanks a lot
-Rajan
    This topic has been closed for replies.

    1 reply

    November 10, 2006
    Looks like a missing library.
    The error you’re seeing is related to a missing GLIBC 3.2, which should be available on a RHAT 4 installation but maybe not on Fedora.

    Try installing it:
    yum install libstdc++.so.5

    If this does not work and the lib is there, is this a 32 or a 64 Bit machine?

    November 10, 2006
    To avoid the follow-up problem:

    Install with the platformWarnOnly option to not have the installer break, because your OS is not supported...

    ./installFMS -platformWarnOnly
    Participant
    February 18, 2007
    Thanks ... just to help others I am posting this ....

    I have AMD x64 dual core and I'm using Fedora Core 6

    I solved my initial missing library error by following another post on this forum:

    quote:

    Originally posted by: phreelancer
    I got FMS working with Fedora by entering these UNIX commands:

    cd /usr/lib
    sudo ln -s libcrypto.so libcrypto.so.4
    sudo ln -s libcrypto.so libcrypto.so.6
    sudo ln -s libssl.so libssl.so.4
    sudo ln -s libssl.so libssl.so.6

    /etc/init.d/fms start

    ALSO, don't forget that you need to have these port numbers opened by your ISP:

    FMS Server Port = 1935
    FMS Admin Server Port = 1111

    Enjoy!


    Then, I followed the solution in this post .... and finally it came to a point where everything was available but it said

    quote:

    [root@localhost FMS_2_0_3_r68_linux]# ./installFMS

    WARNING: Your architecture, \'x86_64\', is not supported by the
    Macromedia Flash Media Server installer.


    I solved that issue by adding the parameter -platformWarnOnly....

    Thanks guys!!!