|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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"
I'm not what you would call conversant with Terminal, so if anyone could help me
with this problem, I'd be grateful.
A.D.B
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Anthony D. Baye" <Sha### [at] spamnomorehotmailcom> 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"
>
> I'm not what you would call conversant with Terminal, so if anyone could help me
> with this problem, I'd be grateful.
>
> A.D.B
Anthony,
I too am having the same issue (although not with OSX) and am looking for a
resolve for this.
I run a Phenom X4 9600 Black Edition (AMD Quad 2.3GHz Unlocked CPU) under Fedora
8 x64 (2.6.24.3-12.fc8) with all the current libraries and updates.
Povray 3.6.1 is installed (and is currently fully functional - although it only
uses a single core per session).
I know this doesn't help you in any way, but at least you can rest assured that
you are not alone with this issue :)
If anyone does know of a solution, I too would be very grateful.
Tanx!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: compiling unix betas under OS X 10.4
Date: 16 Aug 2008 15:56:52
Message: <48a73104@news.povray.org>
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |