[campcaster-support] Boost: Is version 1.33 really necessary and is there a simple way to upgrade fr
  • I'm trying to install Campcaster on a RHES4.0 server and having a
    problem with the boost c++ libraries that Campcaster requires. This is
    hampered by the fact that I know nothing about boost.

    [This is a prototype installation for a new station that is not on the
    air yet. The server does not have a sound card. Our plan is to configure
    it to stream using Jackit (and the instructions at:
    http://code.campware.org/projects/campcaster/wiki/campcasterJack)]

    The install is erring out because my RHES4.0 system has version 1.32 of
    the boost c++ libraries installed when Campcaster is looking for version
    1.33.

    So I've been trying to upgrade my system to boost 1.33 but after
    building it, the resulting collection of .so and .a files looks very
    intimidating. I then found a fedora rpm for boost 1.33 but it has
    dependency problems:
    error: Failed dependencies:
    libstdc++.so.6(GLIBCXX_3.4.5) is needed by boost-1.33.1-6.1.i386
    rtld(GNU_HASH) is needed by boost-1.33.1-6.1.i386
    boost = 1.32.0-1.rhel4 is needed by (installed)
    boost-devel-1.32.0-1.rhel4.i386

    So, I'm wonder how necessary boost 1.33 is and whether I could use 1.32.
    What does Campcaster use boost for? Are there significant differences
    between 1.32 and 1.33? If I were to use 1.32 how would I tell the
    Campcaster install procedure to let me do it?

    Thanks,

    John

    --
    John Hicks

    When replying to me personally, please use "johnhicks" instead of "johnlist" in the email address.
  • 2 Comments sorted by
  • John Hicks wrote on 04/24/2007 01:02 AM:
    > I'm trying to install Campcaster on a RHES4.0 server and having a
    > problem with the boost c++ libraries that Campcaster requires. This is
    ...
    > So I've been trying to upgrade my system to boost 1.33 but after
    > building it, the resulting collection of .so and .a files looks very
    > intimidating. I then found a fedora rpm for boost 1.33 but it has

    Why is it intimidating? Install boost from the boost_1_33_1.tar.bz2
    file downloaded from Sourceforge. Follow the instructions on their
    http://www.boost.org/more/getting_started.html page. It's very simple
    (you really only need the yellow sections 1, 4 and 5), and you don't
    need to even look at those .so and .a files.

    Once
    # bjam "-sTOOLS=gcc" install
    has finished successfully, your 1.33.1 boost library is installed in
    /usr/local, and Campcaster's 'make install' should run without problems.

    Ferenc
  • Ferenc Gerlits wrote:
    > John Hicks wrote on 04/24/2007 01:02 AM:
    >> I'm trying to install Campcaster on a RHES4.0 server and having a
    >> problem with the boost c++ libraries that Campcaster requires. This is
    > ...
    >> So I've been trying to upgrade my system to boost 1.33 but after
    >> building it, the resulting collection of .so and .a files looks very
    >> intimidating. I then found a fedora rpm for boost 1.33 but it has
    >
    > Why is it intimidating? Install boost from the boost_1_33_1.tar.bz2
    > file downloaded from Sourceforge. Follow the instructions on their
    > http://www.boost.org/more/getting_started.html page. It's very simple
    > (you really only need the yellow sections 1, 4 and 5), and you don't
    > need to even look at those .so and .a files.
    >
    > Once
    > # bjam "-sTOOLS=gcc" install
    > has finished successfully, your 1.33.1 boost library is installed in
    > /usr/local, and Campcaster's 'make install' should run without problems.
    >
    > Ferenc
    Thanks, Ferenc. Following your advice, I ran:
    bjam "-sTOOLS=gcc" install
    Doing that installed the libboost .so and .a files in:
    /usr/local/include/boost-1_33_1/boost/
    Then I reran "make install" for campcaster and it was able to find the
    boost library files.

    (The install proceeded from there until it could not find
    "libxml++-2.6". My RHES4.0 system has libxml2.2.6.16 installed. I will
    probably do another post on this problem in a minute.)

    Thanks again for your help.

    John

    --
    John Hicks

    When replying to me personally, please use "johnhicks" instead of "johnlist" in the email address.