Le 17/08/2010 16:08, chris3d nous fit lire :
> Le_Forgeron <lef### [at] freefr> wrote:
>> Le 17/08/2010 14:24, chris3d a écrit :
> 
> Hi,
> 
> thank you for thist fast answer.
> 
>> 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)
> 
> I had to specify those paths. Otherwise I get an incopatible lib error when
> compiling. Fedora uses /usr/lib and /usr/lib64
> 
> 
>> What is your "native" boost library package ? (version ?)
> 
> I have my self-compiled boost1.43 and the installed boost1.41 from the repo.
> The devel package is installed as well.

It's the devel package you will be using when compiling & linking povray.

> 
> 
>> 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!)
> 
> Thank you for this information.
> With: "--with-libboost_thread=mt.so.1.43.0" configure doesn't return errors but
> I get the error when building.

I did also on my time...

> 
> I tried not to use it and build PovRay with installed boost1.41 from the
> repository.
> 
> My configuration:
>  ./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-lib=/usr/lib64/
> 
>  ./configure runs fine with these settings but I have the same issue when
> building.
> 

Oh yes... what does libboost_thread.so link to ? (in /usr/lib64/)

"grep BOOST_ Makefile" give me:

BOOST_CPPFLAGS = -pthread -I/usr/include
BOOST_LDFLAGS = -L/usr/lib
BOOST_THREAD_LIB = -lboost_thread-mt

Now the sad note is that configure seems to have hard-coded ".../lib"
for BOOST_LDFLAGS (and ".../include" for BOOST_CPPFLAGS)

So, if at least you can install the dev-boost in a good looking tree
(foo/lib & foo/include) you might get some easy way with a basic
--with-boost=foo



Side note info: http://blog.julipedia.org/2008/06/lib64-problems.html

Post a reply to this message