Nicolas Calimet <pov### [at] freefr> wrote:
> Anthony D. Baye wrote:
> > I'm trying to compile the Unix beta sources under Tiger and I've installed the
> > boost libraries, the configure is detecting them, but I keep getting a
> > configuration error "Could not link against boost_thread"
>
>  Please mail me the config.log file that configure has generated.
>
>  - NC


Was this problem solved? I'm having the same issue here... I can send the
config.log if desired.

John

PS: and the last linux beta binary won't run because of the "Timed out waiting
for worker thread startup" problem.

Post a reply to this message

>
> Was this problem solved? I'm having the same issue here... I can send the
> config.log if desired.
>
> John
>
> PS: and the last linux beta binary won't run because of the "Timed out waiting
> for worker thread startup" problem.

Mmm. I'm suspecting the problem is due to the fact the 'boost' libraries are
only installed as static (non-shared) versions. Could this be the problem?

John

Post a reply to this message

"John" <http://www.jcoppens.com/misc/mail.php> wrote:

> Mmm. I'm suspecting the problem is due to the fact the 'boost' libraries are
> only installed as static (non-shared) versions. Could this be the problem?
>
> John

Just for the record - and then I'm off to bed, it's 3 AM here:

I installed the shared versions of the boost libraries and still cannot compile
the povray source:

checking for exit in -lboost_thread-mt... no
checking for exit in -lboost_thread-boost_thread-mt... no
configure: error: Could not link against boost_thread-boost_thread-mt !

And, important, but I forgot to mention this: I have this problem on Linux
not MacOS.

John

Post a reply to this message

"John" <http://www.jcoppens.com/misc/mail.php> wrote:

> checking for exit in -lboost_thread-mt... no
> checking for exit in -lboost_thread-boost_thread-mt... no
> configure: error: Could not link against boost_thread-boost_thread-mt !
>
> And, important, but I forgot to mention this: I have this problem on Linux
> not MacOS.
>
> John

Ok. Solved! The Boost package installed the libraries under another name:

libboost_thread-gcc42-mt.so

so povray couldn't find it. I suspect on MacOS something similar must happen.

so I symlinked:

ln -s libboost_thread-gcc42-mt-1_36.so.1.36.0 libboost_thread-mt.so

and config went well. Now I'm having issues with the compilation...

John

Post a reply to this message

John wrote:
> ln -s libboost_thread-gcc42-mt-1_36.so.1.36.0 libboost_thread-mt.so
> 
> and config went well. Now I'm having issues with the compilation...

Yes, you need a pre-1.35 boost.

	Thorsten, POV-Team

Post a reply to this message

On Sat, 16 Aug 2008 09:37:30 +0200
Thorsten Froehlich <tho### [at] trfde> wrote:

> John wrote:
> > ln -s libboost_thread-gcc42-mt-1_36.so.1.36.0 libboost_thread-mt.so
> > 
> > and config went well. Now I'm having issues with the compilation...
> 
> Yes, you need a pre-1.35 boost.

Hello Thorsten,

Is that really necessary - I mean is there another reason besides the
compilation problems?

BTW, the symlink I proposed wasn't the correct solution for compiling.
This only solved the configuring. To also compile correctly, it is just
necessary to do:

./configure COMPILED_BY="your name <email>" \
     --with-boost-thread=boost_thread-gcc42-mt 

This still leaves a runtime timing problem which can be solved by editing
vfesession.cpp as proposed by a mail on the pov-lists.

John

Post a reply to this message

John Coppens wrote:
> On Sat, 16 Aug 2008 09:37:30 +0200
> Thorsten Froehlich <tho### [at] trfde> wrote:
> 
>> John wrote:
>>> ln -s libboost_thread-gcc42-mt-1_36.so.1.36.0 libboost_thread-mt.so
>>>
>>> and config went well. Now I'm having issues with the compilation...
>> Yes, you need a pre-1.35 boost.
> 
> Hello Thorsten,
> 
> Is that really necessary - I mean is there another reason besides the
> compilation problems?

Yes, the boost thread interface changed in 1.35 for certain reasons. You 
absolutely positivity cannot use it.

	Thorsten

Post a reply to this message

On Sat, 16 Aug 2008 21:56:50 +0200
Thorsten Froehlich <tho### [at] trfde> wrote:

> > Is that really necessary - I mean is there another reason besides the
> > compilation problems?
> 
> Yes, the boost thread interface changed in 1.35 for certain reasons.
> You absolutely positivity cannot use it.

I really _hate_ to insist - I asked about reasons, because I got POV
3.7 compiled with Boost 1.36, and it seems to work normally. 

Shouldn't there be execution problems, or has this only effect on the
image quality/contents?

John

Post a reply to this message

John Coppens wrote:
> On Sat, 16 Aug 2008 21:56:50 +0200
> Thorsten Froehlich <tho### [at] trfde> wrote:
> 
>>> Is that really necessary - I mean is there another reason besides the
>>> compilation problems?
>> Yes, the boost thread interface changed in 1.35 for certain reasons.
>> You absolutely positivity cannot use it.
> 
> I really _hate_ to insist - I asked about reasons, because I got POV
> 3.7 compiled with Boost 1.36, and it seems to work normally. 

This is a complex boost change, not a change in POV-Ray. Please read the 
*boost* documentation, as this is not a POV-Ray issue! Do no use boost 1.35 
or later with the current POV-Ray 3.7 beta source code if you want a 
functional executable. The fact that a program compiles and links does not 
make it function correctly. There is nothing wrong with either boost 1.36 or 
POV-Ray 3.7, you just have to use the correct version of boost. Use boost 
1.34 with the current POV-Ray 3.7 beta source code.

	Thorsten, POV-Team

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
> John Coppens wrote:
> > On Sat, 16 Aug 2008 09:37:30 +0200
> > Thorsten Froehlich <tho### [at] trfde> wrote:
> >
> >> John wrote:
> >>> ln -s libboost_thread-gcc42-mt-1_36.so.1.36.0 libboost_thread-mt.so
> >>>
> >>> and config went well. Now I'm having issues with the compilation...
> >> Yes, you need a pre-1.35 boost.
> >
> > Hello Thorsten,
> >
> > Is that really necessary - I mean is there another reason besides the
> > compilation problems?
>
> Yes, the boost thread interface changed in 1.35 for certain reasons. You
> absolutely positivity cannot use it.
>
>  Thorsten

Hello,
I am using 1.39 version now, and I met the same issue on using libboost_thread
even I use ln -s command. any guys can help me how to do that?
My email address is wis### [at] intelcom
I am using below command:
.../configure --prefix=/home/spd/wchen18/povray/povray-3.7.0.beta.32
--with-boost=/net/spd64/home/spd/wchen18/povray/libs/boost_1_39_0/stage/lib
--with-boost-thread=libboost_thread-gcc43-mt  COMPILED_BY="Wise Chen"

and below are parts error messages:

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 whether to build the boost thread library from sources... no
checking for boostlib >= 1.35... configure: error: We could not detect the boost
libraries (version 1.35 or higher). If you have a staged boost library (still
not installed) please specify $BOOST_ROOT in your environment and do not give a
PATH to --with-boost option.  If you are sure you have boost installed, then
check your version number looking in <boost/version.hpp>. See
http://randspringer.de/boost for more documentation.


Thanks,
Wise

Post a reply to this message