POV-Ray : Newsgroups : povray.unix : Cannot link boost thread (libboost v1.59) : Re: Cannot link boost thread (libboost v1.59) Server Time
26 Apr 2024 07:10:59 EDT (-0400)
  Re: Cannot link boost thread (libboost v1.59)  
From: clipka
Date: 26 Nov 2015 06:05:00
Message: <web.5656e6f040b64f6ad6fa18f0@news.povray.org>
"MadKairon" <nomail@nomail> wrote:
> clipka <ano### [at] anonymousorg> wrote:
> > Am 25.11.2015 um 20:01 schrieb MadKairon:
> > > Still trying to compile Master Branch on Raspbian Jessie. As the boost
> > > distribution in the repositry didn't work I removed it, downloaded libboost 1.59
> > > and installed it. ./prebuild.sh goes ok, then configure process fails when
> > > checking boost thread and stops. This is the new error. Is there any way to fix
> > > it?
> >
> > Maybe. Or maybe not. We'd need to...:
> >
> > > See `config.log' for more details
> >
> > ;)
>
> Errr... well, that was the first thing I tried. All I can say is the words
> "Fatal error" repeat a few times. Sorry, n00b here!
>
> This is the config.log file when I try ./configure COMPILED_BY="MadKairon on RPi
> 2"
>
> http://www.kungfuzn.com.ar/imagenes/config.log

It might be all Greek to you, but it sometimes gives us a clue over here ;)

The "Fatal error" messages in config.log are not necessarily a reason for
concern: The ./configure script tries to compile some small test programs to
figure out how the build environment behaves, and sometimes it needs a few
attempts before it finds the correct combination of parameters to achieve some
desired effect; also, some of the test programs deliberately can't compile, to
see how the build environment reacts to errors.


In your case, what I see is that your linker appears to be convinced that the
boost library should have the file name libboost_thread.so.1.59.0, while in
reality there doesn't seem to be a library file of that exact name.

I gather from your original post that you have built the boost 1.59 library
yourself, rather than download it via a package maneger.

The internet claims that running "sudo ldconfig" might solve your problem.

Alternatively, you could figure out the actual name of the library file, and
link specifically to that file using the --with-boost-thread parameter.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.