I tried to compile the most recent unix source today (the package and 
source are both b29 even though the main beta page says the source is 
for 31), and can't seem to get it the configure script to find the boost 
libraries.
I'm running a fully updated ArchLinux system, and I installed boost 1.37 
from the official package manager, and configure failed at checking for 
exit in boost_thread-lboost_thread.
I then installed boost 1.38 from source, (after removing it with the 
package manager), and got the same error. I tried the config option 
'--with-boost-thread=libboost_thread_gcc43-mt' because that is the name 
of the library on my system, but it still doesn't work.
Do I need to have the location of the libraries in my $PATH or 
something? They are all in the standard /usr/local/lib/, so I didn't 
expect it to be weird.

Thanks for any help!
Chris

(I can provide a config.log file if needed, but won't put it inline here)

Post a reply to this message

CShake <cshake+pov### [at] gmailcom> wrote:
> I'm running a fully updated ArchLinux system, and I installed boost 1.37
> from the official package manager, and configure failed at checking for
> exit in boost_thread-lboost_thread.
> I then installed boost 1.38 from source, (after removing it with the
> package manager), and got the same error. I tried the config option
> '--with-boost-thread=libboost_thread_gcc43-mt' because that is the name
> of the library on my system, but it still doesn't work.

Did you verify that POV's ./configure script can locate all the boost header
files?

Post a reply to this message

clipka wrote:
> CShake <cshake+pov### [at] gmailcom> wrote:
>> I'm running a fully updated ArchLinux system, and I installed boost 1.37
>> from the official package manager, and configure failed at checking for
>> exit in boost_thread-lboost_thread.
>> I then installed boost 1.38 from source, (after removing it with the
>> package manager), and got the same error. I tried the config option
>> '--with-boost-thread=libboost_thread_gcc43-mt' because that is the name
>> of the library on my system, but it still doesn't work.
> 
> Did you verify that POV's ./configure script can locate all the boost header
> files?
> 
> 
> 
I assume it can find the headers, since it's installed in the standard 
location (/usr/local/lib/) and a few lines above the error it shows 
"checking whether the Boost::Thread library is available... yes".

I also tried to build it with just the boost source, 
(--with-boost-src=/home/cshake/Downloads/boost_1_38_0/) and ./configure 
works fine, but make dies saying
"*** No rule to make target 
'/home/cshake/Downloads/boost_1_38_0/libs/thread/src/barrier.cpp', 
needed by 'barrier.o'. Stop".
I looked at that folder and there is no such file 'barrier.cpp' in that 
folder or any subfolder, so I am confused.


Chris

Post a reply to this message

(CShake) :

> I then installed boost 1.38 from source, (after removing it with the 
> package manager), and got the same error. I tried the config option 
> '--with-boost-thread=libboost_thread_gcc43-mt' because that is the name 
> of the library on my system, but it still doesn't work.
>
try '--with-boost-thread=boost_thread_gcc43-mt'

> Chris

Regards,
Slawek
-- 
  ________ 
_/ __/ __/ Zenon Sienkiewicz skrzywdzil Justyne z dwu stron.
 \__ \__ \_______________________________________________________________
 /___/___/ S�awomir Szczyrba                          steev/AT/hot\dot\pl

Post a reply to this message

S�awomir Szczyrba wrote:
> (CShake) :
> 
>> I then installed boost 1.38 from source, (after removing it with the 
>> package manager), and got the same error. I tried the config option 
>> '--with-boost-thread=libboost_thread_gcc43-mt' because that is the name 
>> of the library on my system, but it still doesn't work.
>>
> try '--with-boost-thread=boost_thread_gcc43-mt'
> 
>> Chris
> 
> Regards,
> Slawek

Thanks, that works for boost.

Now it is throwing errors on zlib,
"checking whether to use the ZLIB library... yes
checking for library containing zlibVersion... -lz
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for libz version >= 1.2.1... unknown
configure: error: cannot find a suitable ZLIB library"

I know I have zlib 1.2.3 installed, and I tried 
'--with-zlib=/usr/include/' (where zlib.h is) and --with-zlib=/var/lib/' 
(where libz.so is), neither of which work.

I don't usually have problems compiling anything, boost configured fine 
and everything else I run from source has worked (once dependencies are 
installed)

Post a reply to this message

"CShake" <cshake+pov### [at] gmailcom> wrote in message 
news:49ac0720$1@news.povray.org...

> I know I have zlib 1.2.3 installed, and I tried 
> '--with-zlib=/usr/include/' (where zlib.h is) and --with-zlib=/var/lib/' 
> (where libz.so is), neither of which work.

Is Zlib installed as shared lib? I forget the configure switch I used to 
install as shared lib. The rest of my install (LAMP server) went fine after 
I did this, so mabye it's worth looking into.

Jim

Post a reply to this message

CShake wrote:
> I know I have zlib 1.2.3 installed, and I tried
> '--with-zlib=/usr/include/' (where zlib.h is) and --with-zlib=/var/lib/'
> (where libz.so is), neither of which work.

Ah those are tricky paths. When you give --with-zlib=/somewhere, it will
search for includes in /somewhere/include and for the library
in /somewhere/lib. I don't know what to do if you have one in /var and
another in /usr... Symlinks?

Post a reply to this message

Nicolas Alvarez wrote:
> CShake wrote:
>> I know I have zlib 1.2.3 installed, and I tried
>> '--with-zlib=/usr/include/' (where zlib.h is) and --with-zlib=/var/lib/'
>> (where libz.so is), neither of which work.
> 
> Ah those are tricky paths. When you give --with-zlib=/somewhere, it will
> search for includes in /somewhere/include and for the library
> in /somewhere/lib. I don't know what to do if you have one in /var and
> another in /usr... Symlinks?

Oops, I looked again and the /var/lib tree was the package manager temp 
files, not the installed. libz.so and libz.a are in /usr/lib as well. I 
tried --with-zlib=/usr/ [with and without the trailing slash], with the 
same results.
I may just give up for now and wait for the next official build of the 
beta, I just hoped to use my file/web server box for long renders, since 
it's got a decent dual-core CPU.

@Jim - ZLib is a shared library, libz.so.1.2.3.3 is the main file, and 
libz.so.1 and libz.so are both symlinks to it. libz.a also exists in 
/usr/lib
Did you need to use extra switches to install ZLib as shared, or to 
install povray using shared libs?

Post a reply to this message

"CShake" <cshake+pov### [at] gmailcom> wrote in message 
news:49ade1a4$1@news.povray.org...
> @Jim - ZLib is a shared library, libz.so.1.2.3.3 is the main file, and 
> libz.so.1 and libz.so are both symlinks to it. libz.a also exists in 
> /usr/lib
> Did you need to use extra switches to install ZLib as shared, or to 
> install povray using shared libs?

My apologies if I've confused the issue .....

My Zlib problem was not related to installing the POV-Ray application (beta 
or otherwise).

My problem was with installing ImageMagik on my LAMP server. Like you I 
thought I had Zlib installed just fine and tried several things until I hit 
upon the --shared switch (configure) and just thought it was worth a shot 
offering that idea to the discussion.

Good Luck!

Jim

Post a reply to this message

Klik-klik-klik... To CShake pisze :
>
> Now it is throwing errors on zlib,
> "checking whether to use the ZLIB library... yes
> checking for library containing zlibVersion... -lz
> checking zlib.h usability... yes
> checking zlib.h presence... yes
> checking for zlib.h... yes
> checking for libz version >= 1.2.1... unknown

Is zlib-devel installed?

S�awek
-- 
  ________ 
_/ __/ __/ Mniej nale�y obawia� si� g�odu ni� z�ych my�li. -- Henryk Mann
 \__ \__ \_______________________________________________________________
 /___/___/ S�awomir Szczyrba                          steev/AT/hot\dot\pl

Post a reply to this message

> 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

Post a reply to this message

On Mon, 02 Mar 2009 11:19:39 -0500, CShake wrote:

> I know I have zlib 1.2.3 installed, and I tried
> '--with-zlib=/usr/include/' (where zlib.h is) and --with-zlib=/var/lib/'
> (where libz.so is), neither of which work.

While it looks like you do, can you confirm that you have the zlib devel 
package installed as well?

Jim

Post a reply to this message

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

Post a reply to this message

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

> 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

	So linking is successful since the boost thread lib is indeed found
under /usr/local/lib.

> 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

	Now this is the sign that something is wrong at runtime, i.e. as if
/usr/local/lib is not set in the default search path for the runtime linker.
You may check with ldconfig whether this is the case.  For testing before
having to modify your system setup, you may try using LD_LIBRARY_PATH
(e.g. export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH) before running
configure and (hopefully) the povray binary.

	- NC

Post a reply to this message

> 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?

	This path was guessed by configure as a possible search path for
the boost libs after failing looking in "standard" directories.  It won't
harm to search a non-existing path for include files, however that means
maybe the boost install is somewhat screwed.  What is the actual location
of the boost 1.38 headers on your system?

	- NC

Post a reply to this message

Nicolas Calimet wrote:
>> 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?
> 
>     This path was guessed by configure as a possible search path for
> the boost libs after failing looking in "standard" directories.  It won't
> harm to search a non-existing path for include files, however that means
> maybe the boost install is somewhat screwed.  What is the actual location
> of the boost 1.38 headers on your system?
> 
>     - NC
All the .a and .so libraries are in /usr/local/lib/, and all the .hpp 
headers are in /usr/local/include/boost-1_38/boost/ (and subdirectories)

Boost was installed from source without any extra configure switches, 
just $ ./configure and $ sudo make install.

Post a reply to this message

OK, guess this is just due to the pov-team only officially supporting 
boost 1.37 and not 1.38. I removed all the 1.38 files that were built 
from source, and installed 1.37 from pacman (the ArchLinux repository 
system), and it worked fine only having to change the name of the thread 
library to boost_thread-mt.

Guess this whole thread can be ignored now, or maybe just as a caution 
to not use 1.38.

cshake

CShake wrote:
> Nicolas Calimet wrote:
>>> 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?
>>
>>     This path was guessed by configure as a possible search path for
>> the boost libs after failing looking in "standard" directories.  It won't
>> harm to search a non-existing path for include files, however that means
>> maybe the boost install is somewhat screwed.  What is the actual location
>> of the boost 1.38 headers on your system?
>>
>>     - NC
> All the .a and .so libraries are in /usr/local/lib/, and all the .hpp 
> headers are in /usr/local/include/boost-1_38/boost/ (and subdirectories)
> 
> Boost was installed from source without any extra configure switches, 
> just $ ./configure and $ sudo make install.

Post a reply to this message

> Guess this whole thread can be ignored now, or maybe just as a caution 
> to not use 1.38.

	No, (under linux at least) 1.38 works as well as any boost version since 1.35.

>> All the .a and .so libraries are in /usr/local/lib/, and all the .hpp 
>> headers are in /usr/local/include/boost-1_38/boost/ (and subdirectories)

	Ok, indeed this is what happens by default when installing boost from sources.
Just create a symlink then, e.g.
sudo ln -s /usr/local/include/boost-1_38/boost /usr/local/include/boost

	- NC

Post a reply to this message