Hi I'm currently facing issues when compiling POV-Ray for Centos 5.10.

The issue is that I have issues linking with the boost library.

I have downloaded boost 1.41 in bz2 form seeing how there were issues with the
1.50 version of the libraries. Then I proceeded to only install the thread
libraries.

However, there were issues with linking the boost thread libraries. Below is the
output from the failed ./configure execution.

Environment
-----------
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether $C_INCLUDE_PATH contains the "." path... no
checking whether $CPLUS_INCLUDE_PATH contains the "." path... no

Programs
--------
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdlib.h... (cached) yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether the g++ compiler works... yes
checking how to run the C++ preprocessor... g++ -E
checking for C++ compiler vendor... gnu
checking for g++ version... 4.1.2
checking for ranlib... ranlib

Libraries
---------
checking whether to link with cygwin DLL... no
checking whether to enable static linking... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for boostlib >= 1.37... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread... yes
checking whether the boost thread library is usable... no
configure: error: cannot link with the boost thread library
See `config.log' for more details.


Forgive me if I don't know how to format the excerpt, I'm new here.

Post a reply to this message

On 12/02/14 00:59, Excentp wrote:
> 
> 
> Forgive me if I don't know how to format the excerpt, I'm new here.
> 
> 

I don't have CentOS so I can't check this but have you tried:

./configure COMPILED_BY="Your Name <your.email>"
--with-boost-thread=boost_thread-mt LIBS="-lboost_system -lboost_thread"

John
-- 
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children

Post a reply to this message

Doctor John wrote:

> On 12/02/14 00:59, Excentp wrote:
>> 
>> 
>> Forgive me if I don't know how to format the excerpt, I'm new here.
>> 
>> 
> 
> I don't have CentOS so I can't check this but have you tried:
> 
> ./configure COMPILED_BY="Your Name <your.email>"
> --with-boost-thread=boost_thread-mt LIBS="-lboost_system -lboost_thread"
> 
> John

And try boost 1.53
-- 

Ger

Post a reply to this message

Ger <No.### [at] ThankYou> wrote:
> Doctor John wrote:
> > On 12/02/14 00:59, Excentp wrote:
> >>
> >>
> >> Forgive me if I don't know how to format the excerpt, I'm new here.
> >>
> >>
> >
> > I don't have CentOS so I can't check this but have you tried:
> >
> > ./configure COMPILED_BY="Your Name <your.email>"
> > --with-boost-thread=boost_thread-mt LIBS="-lboost_system -lboost_thread"
> >
> > John
>
> And try boost 1.53
> --
>
> Ger

Why are there so many issues with linking to boost? I've encountered them before
on some systems despite other systems running the same OS not having issues.
Just doesn't make any sense. My current issue (which I've only superficially
looked into) is a Debian system not being able to make static binaries while the
Ubuntu one can even though the Debian system has all the appropriate *.a
libraries.

Post a reply to this message

Le 12/02/2014 08:01, jhu a écrit :
> Why are there so many issues with linking to boost?

because boost is rather a collection of template and utilities.
Only a few components are actually a true library. And they appears to
have a bit of instability about handling dependencies since 1.40 (it's a
bit complex, and they rename some libraries too... and move components)

The sad part: povray actually need to use the part of boost which are in
library.

The nice part: if povray move to C++11 (not expecting retrocompatibility
with old C++03 or older C++98), the thread is now part of the standard,
and that part of boost might be dropped.
But that's a major break with platforms not providing C++11.

-- 
Just because nobody complains does not mean all parachutes are perfect.

Post a reply to this message

jhu wrote:

> Ger <No.### [at] ThankYou> wrote:
>> Doctor John wrote:
>> > On 12/02/14 00:59, Excentp wrote:
>> >>
>> >>
>> >> Forgive me if I don't know how to format the excerpt, I'm new here.
>> >>
>> >>
>> >
>> > I don't have CentOS so I can't check this but have you tried:
>> >
>> > ./configure COMPILED_BY="Your Name <your.email>"
>> > --with-boost-thread=boost_thread-mt LIBS="-lboost_system
>> > -lboost_thread"
>> >
>> > John
>>
>> And try boost 1.53
>> --
>>
>> Ger
> 
> Why are there so many issues with linking to boost? 

I know that boost 1.50 had some problems but other than that I have no clue
whatsoever.
But what I do know is that the little script I posted to compile Povray on OpenSuse
works like a charm.
It most likely won't work straight out of the box on Debian but it lists all libs you
need to create a fully functional Povray, including preview window.

-- 

Ger

Post a reply to this message

On 02/12/2014 02:57 AM, Ger wrote:
> jhu wrote:
>
>> Ger <No.### [at] ThankYou> wrote:
>>> Doctor John wrote:
>>>> On 12/02/14 00:59, Excentp wrote:
>>>>>
>>>>>
>>>>> Forgive me if I don't know how to format the excerpt, I'm new here.
>>>>>
>>>>>
>>>>
>>>> I don't have CentOS so I can't check this but have you tried:
>>>>
>>>> ./configure COMPILED_BY="Your Name <your.email>"
>>>> --with-boost-thread=boost_thread-mt LIBS="-lboost_system
>>>> -lboost_thread"
>>>>
>>>> John
>>>
>>> And try boost 1.53
>>> --
>>>
>>> Ger
>>
>> Why are there so many issues with linking to boost?
>
> I know that boost 1.50 had some problems but other than that I have no clue
whatsoever.
> But what I do know is that the little script I posted to compile Povray on OpenSuse
works like a charm.
> It most likely won't work straight out of the box on Debian but it lists all libs
you need to create a fully functional Povray, including preview window.
>

On my personal machine (older 32bit dual core opensuse) I'm using < 1.5 
boost and /never/ had problems getting preview window using libsdl

On the buildbot server that I've been working on (emulates latest ubuntu 
64 bit ... in a rackspace setup) I'm using 1.53 boost and the other libs 
that I mentioned while trying to help with Yadgar's issues. Right now 
I'm only watching pov/uber github repos and /eventually/ hope to make 
those build results (the binaries) available for download.

Post a reply to this message