Springlobby fails to compile

Springlobby fails to compile

Discuss everything related to running Spring on your chosen distribution of Linux.

Moderator: Moderators

Post Reply
HAARP
Posts: 182
Joined: 06 Apr 2006, 07:18

Springlobby fails to compile

Post by HAARP »

Springlobby always compiled fine, but the latest one fails. (latest as in, latest in the Spring overlay)

Code: Select all

/usr/lib64/libtorrent.so: undefined reference to `boost::recursive_mutex::do_lock()'
/usr/lib64/libtorrent.so: undefined reference to `boost::detail::condition_impl::condition_impl()'
/usr/lib64/libtorrent.so: undefined reference to `boost::detail::condition_impl::do_wait(pthread_mutex_t*)'
/usr/lib64/libtorrent.so: undefined reference to `boost::mutex::do_lock()'
/usr/lib64/libtorrent.so: undefined reference to `boost::recursive_mutex::do_unlock()'
/usr/lib64/libtorrent.so: undefined reference to `boost::recursive_mutex::do_unlock(boost::recursive_mutex::cv_state&)'
/usr/lib64/libtorrent.so: undefined reference to `boost::detail::condition_impl::do_timed_wait(boost::xtime const&, pthread_mutex_t*)'
/usr/lib64/libtorrent.so: undefined reference to `boost::mutex::do_lock(boost::mutex::cv_state&)'
/usr/lib64/libtorrent.so: undefined reference to `boost::recursive_mutex::do_lock(boost::recursive_mutex::cv_state&)'
/usr/lib64/libtorrent.so: undefined reference to `boost::recursive_mutex::~recursive_mutex()'
/usr/lib64/libtorrent.so: undefined reference to `boost::mutex::~mutex()'
/usr/lib64/libtorrent.so: undefined reference to `boost::thread::sleep(boost::xtime const&)'
/usr/lib64/libtorrent.so: undefined reference to `boost::thread::thread(boost::function0<void, std::allocator<boost::function_base> > const&)'
/usr/lib64/libtorrent.so: undefined reference to `boost::mutex::do_unlock()'
/usr/lib64/libtorrent.so: undefined reference to `boost::xtime_get(boost::xtime*, int)'
/usr/lib64/libtorrent.so: undefined reference to `boost::recursive_mutex::recursive_mutex()'
/usr/lib64/libtorrent.so: undefined reference to `boost::mutex::do_unlock(boost::mutex::cv_state&)'
/usr/lib64/libtorrent.so: undefined reference to `boost::mutex::mutex()'
/usr/lib64/libtorrent.so: undefined reference to `boost::filesystem::detail::status_api(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int&)'
/usr/lib64/libtorrent.so: undefined reference to `boost::detail::condition_impl::notify_all()'
/usr/lib64/libtorrent.so: undefined reference to `boost::detail::condition_impl::~condition_impl()'
/usr/lib64/libtorrent.so: undefined reference to `boost::detail::condition_impl::notify_one()'
collect2: ld returned 1 exit status
make[2]: *** [springlobby] Error 1
make[2]: Leaving directory `/var/tmp/portage/games-util/springlobby-0.0.1.10352/work/springlobby-0.0.1.10352'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/games-util/springlobby-0.0.1.10352/work/springlobby-0.0.1.10352'
make: *** [all] Error 2
No idea what could be causing this. boost is installed properly (1.35.0). I suspect that the Springlobby ebuild depends on an older version of libboost but needs a newer one.
User avatar
Cremuss
Posts: 364
Joined: 28 Oct 2006, 21:38

Re: Springlobby fails to compile

Post by Cremuss »

same here :/
Auswaschbar
Spring Developer
Posts: 1254
Joined: 24 Jun 2007, 08:34

Re: Springlobby fails to compile

Post by Auswaschbar »

HAARP wrote:Springlobby always compiled fine, but the latest one fails. (latest as in, latest in the Spring overlay)

Code: Select all

stuff
No idea what could be causing this. boost is installed properly (1.35.0). I suspect that the Springlobby ebuild depends on an older version of libboost but needs a newer one.
I didn't change anything in the ebuild, i just copy it over for each new version. Did seems to be a problem with rb_libtorrent, try to re-emerge it.
User avatar
Cremuss
Posts: 364
Joined: 28 Oct 2006, 21:38

Re: Springlobby fails to compile

Post by Cremuss »

Yep that worked !
I just re-emerged rb_libtorrent.
HAARP
Posts: 182
Joined: 06 Apr 2006, 07:18

Re: Springlobby fails to compile

Post by HAARP »

Looks like the update to boost 1.35.0 broke rb_libtorrent. Can't even recompile it

rb_libtorrent says:

Code: Select all

configure: error: Unable to find Boost.Filesystem library, currently this is required.
Can't figure out what USE flag causes boost to compile in Boost.Filesystem...
Cremuss, give me your USE flags for boost please.


On a related note, the Springlobby ebuild should use the bittorrent USE-flag instead of creating its own disable-torrent. Also needs to invert the behavior if this was to be fixed.
Same goes for disable-sound. Invert it and name it just sound
Not that it really matters, but this way you're in line with all the official Ebuilds. See here
User avatar
Cremuss
Posts: 364
Joined: 28 Oct 2006, 21:38

Re: Springlobby fails to compile

Post by Cremuss »

[ebuild R ] dev-util/boost-build-1.35.0-r1 USE="python -examples" 0 kB
[ebuild R ] dev-libs/boost-1.35.0-r2 USE="-debug -doc -expat -icu -mpi -tools" 0 kB
HAARP
Posts: 182
Joined: 06 Apr 2006, 07:18

Re: Springlobby fails to compile

Post by HAARP »

Auswaschbar
Spring Developer
Posts: 1254
Joined: 24 Jun 2007, 08:34

Re: Springlobby fails to compile

Post by Auswaschbar »

HAARP wrote:On a related note, the Springlobby ebuild should use the bittorrent USE-flag instead of creating its own disable-torrent. Also needs to invert the behavior if this was to be fixed.
Same goes for disable-sound. Invert it and name it just sound
Not that it really matters, but this way you're in line with all the official Ebuilds. See here
It used to be that way some time ago. But Springlobby maintainer asked for it to be enabled by default, so I changed it this way.
HAARP
Posts: 182
Joined: 06 Apr 2006, 07:18

Re: Springlobby fails to compile

Post by HAARP »

Auswaschbar wrote:
HAARP wrote:On a related note, the Springlobby ebuild should use the bittorrent USE-flag instead of creating its own disable-torrent. Also needs to invert the behavior if this was to be fixed.
Same goes for disable-sound. Invert it and name it just sound
Not that it really matters, but this way you're in line with all the official Ebuilds. See here
It used to be that way some time ago. But Springlobby maintainer asked for it to be enabled by default, so I changed it this way.
It's up to the user to take care of his USE-flags. Although I agree that enabling by default is the correct behavior, the ebuild shouldn't veer from established standards to ensure that it is. Otherwise we'd have a lot of confusing USE-flags in just about every package
Post Reply

Return to “Linux”