POV-Ray : Newsgroups : povray.beta-test : problems linking to boost libraries (linux) : Re: problems linking to boost libraries (linux) Server Time
28 Jul 2024 18:15:56 EDT (-0400)
  Re: problems linking to boost libraries (linux)  
From: CShake
Date: 10 Mar 2009 16:22:26
Message: <49b6cc02@news.povray.org>
CShake wrote:
> Nicolas Calimet wrote:
>>> checking for zlib.h... yes
>>> checking for libz version >= 1.2.1... unknown
>>> configure: error: cannot find a suitable ZLIB library"
>>
>>     In fact this might not be a problem with zlib, but something else
>> in the compiler command-line might prevent liking the test binary that 
>> checks
>> for the libz version.
>>     In other words, you must check the config.log file to see the actual
>> error; search for "libz version" (without quotes) to jump slightly above
>> the error message.
>>
>>     - NC
> 
> You are correct, after digging in config.log I see that it is once again 
> a boost problem:
> 
> configure:8561: checking for libz version >= 1.2.1
> configure:8593: g++ -o conftest  -pthread -I/usr/lib/../include -pthread 
> -I/usr/local/include/boost-1_38 -L/usr/lib  -L/usr/local/lib 
> conftest.cpp -lz -lrt -lm -lboost_thread-gcc43-mt  -pthread  >&5
> configure:8596: $? = 0
> configure:8602: ./conftest
> ./conftest: error while loading shared libraries: 
> libboost_thread-gcc43-mt-1_38.so.1.38.0: cannot open shared object file: 
> No such file or directory
> 
> This error confuses me as well, because 
> /usr/local/lib/libboost_thread-gcc43-mt-1_38.so.1.38.0 exists, with 
> permissions -rwxr-xr-x u:root g:root, so it shouldn't have trouble 
> reading the .so
> 
> cshake

Well, just downloaded the b31 source and tried again, this time with it 
dying at 'checking if boost thread library is usable', but with the same 
reasons.
config.log shows the same errors. I'm confused why the switch 
'-I/usr/local/include/boost-1_38' exists, since my calling line is
'$ ./configure COMPILED_BY=cshake <cshake+pov### [at] gmailcom> 
--with-boost=/usr/local --with-boost-thread=boost_thread-gcc43-mt', 
nowhere do I say that boost is within the 'boost-1_38' subdir, because 
it isn't. Do I need to create that subdirectory with symbolic links in 
it, or edit the configure script to not add the extra path?


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.