[libtorrent] Boost::Chrono library error while installing Libtorrent 1.1.3 from source

[Ronald Degmar]

Hi Arvid,

I upgraded from libtorrent version 1.0.10 to version 1.1.3.
While building libtorrent from source on centos, fedora and debian, I got a
new error. This is as follows:

Checking for boost libraries:
checking for boostlib >= 1.53... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono... no
checking for exit in -lboost_chrono... (cached) no
checking for exit in -lboost_chrono... (cached) no
configure: error: Could not link against boost_chrono !
libtorrent: cmmi failed: /tmp/tmpOJAB8Nbuildout-libtorrent

Building on Ubuntu passed successfully

Checking for boost libraries:
checking for boostlib >= 1.53... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono... yes
checking whether the Boost::Random library is available... yes
checking for exit in -lboost_random... yes

Why did I get that error?
These are the configure options I'm using:

--enable-python-binding --disable-dependency-tracking
--disable-silent-rules PYTHON=${PY}/python --prefix=${AT_HOME}
--with-boost=${AT_HOME} --with-libiconv --with-boost-python=boost_python
BOOST_ROOT=\"${PKG}/${_BOOST_DIR}\""

Ronald Barrios

[Arvid Norberg]

Post by Ronald Degmar
Hi Arvid,
I upgraded from libtorrent version 1.0.10 to version 1.1.3.
While building libtorrent from source on centos, fedora and debian, I got a
checking for boostlib >= 1.53... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono... no
checking for exit in -lboost_chrono... (cached) no
checking for exit in -lboost_chrono... (cached) no
configure: error: Could not link against boost_chrono !
libtorrent: cmmi failed: /tmp/tmpOJAB8Nbuildout-libtorrent
[...]
Why did I get that error?

your config.log may reveal some hints. perhaps the chrono library is a
separate package on centos that needs to be installed. perhaps it has a
naming convention that's not supported by the m4 file that comes with
libtorrent. perhaps upgrading that would make it work.

[Ronald Degmar]

That doesn't happen with libtorrent 1.0.10.
Is this "exit" new in libtorrent 1.1.3??

Post by Arvid Norberg

Post by Ronald Degmar
Hi Arvid,
I upgraded from libtorrent version 1.0.10 to version 1.1.3.
While building libtorrent from source on centos, fedora and debian, I

got a

Post by Ronald Degmar
checking for boostlib >= 1.53... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Chrono library is available... yes
checking for exit in -lboost_chrono... no
checking for exit in -lboost_chrono... (cached) no
checking for exit in -lboost_chrono... (cached) no
configure: error: Could not link against boost_chrono !
libtorrent: cmmi failed: /tmp/tmpOJAB8Nbuildout-libtorrent
[...]
Why did I get that error?

your config.log may reveal some hints. perhaps the chrono library is a
separate package on centos that needs to be installed. perhaps it has a
naming convention that's not supported by the m4 file that comes with
libtorrent. perhaps upgrading that would make it work.
--
Arvid Norberg
------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libtorrent-discuss mailing list
https://lists.sourceforge.net/lists/listinfo/libtorrent-discuss

[Arvid Norberg]

Post by Ronald Degmar
That doesn't happen with libtorrent 1.0.10.

I don't know what "that" refers to here.

Post by Ronald Degmar
Is this "exit" new in libtorrent 1.1.3??

I assume that's a config test, part of either autotools/autoconf or the m4
script for boost-chrono. I'm involved in neither.

You may want to understand how one links against boost.chrono out of the
package manager on centos, then compare that to what the configuration test
is doing.