Le 17/08/2010 14:24, chris3d a écrit :
> Hello,
> 
> I'm having some difficulties with building povray-3.7.0.beta.38 with Fedora 13
> 64-bit.
> 
> These are my POV-Ray specific configure options:
> ../configure COMPILED_BY="Chris3D <inf### [at] flare3dde>" --with-libpng=/usr/lib64
> --with-zlib=/usr/lib64 --with-libjpeg=/usr/lib64 --with-libtiff=/usr/lib64
> --with-openexr=/usr/lib64 --with-libsdl=/usr/lib64 --with-libmkl=/usr/lib64
> 

I wonder why you need to push /usr/lib64 to compile natively.
(but how could I know, I use a 64bit ubuntu... with only COMPILED_BY &
--disable-io-restrictions (personal taste), nothing more)

What is your "native" boost library package ? (version ?)

> 
> Itried with my own boost build (boost 1.43):

Ah ah! We are on something...

> 
> ../bootstrap.sh --prefix=/home/chris/Programme/boost
> --libdir=/home/chris/Programme/boost/lib
> ../bjam install
> 
> Then I configured PovRay like this:
> 
> ../configure COMPILED_BY="Chris3D <inf### [at] flare3dde>" --with-libpng=/usr/lib64
> --with-zlib=/usr/lib64 --with-libjpeg=/usr/lib64 --with-libtiff=/usr/lib64
> --with-openexr=/usr/lib64 --with-libsdl=/usr/lib64 --with-libmkl=/usr/lib64
> --with-boost=/home/chris/Programme/boost/
> --with-boost-lib=/home/chris/Programme/boost/lib/
> 
> That gives me:
> configure: error: cannot link with the boost thread library
> 
> I tried with:
> --with-boost-thread=/home/chris/Programme/boost/lib/libboost_thread.so
> 
> But:
> configure: error: Could not link against
> boost_thread-/home/chris/Programme/boost/lib/libboost_thread.so !
> 
> Maybe you can help me. Thank you in advance.

the switch for boost in configure are more than tricky.
For instance, --with-boost-thread=XXX would use the file named
libboost_thread-XXX (from default location of lib!)
Typical usage would be --with-boost-thread=mt.so.1.40.0
(in fact, typical would be to NOT use it!)

Also, from my bogus memory, I seems to recall that shared libraries must
be trusted to get linked, which usually means that if you install away
from usual place, the linking system must be updated: ld.so.conf should
get extended and ldconfig called to flush that (and that's a work for
root, beware, you can screw your system)
If you only install in usual places (already trusted directory), then
only ldconfig need to be called.



-- 
Real software engineers work from 9 to 5, because that is<br/>
the way the job is described in the formal spec.  Working<br/>
late would feel like using an undocumented external procedure.

Post a reply to this message