POV-Ray : Newsgroups : povray.binaries.images : Following a tutorial on radiosity... : Re: Compiling POV-Ray 3.7 for Linux Server Time
30 Jul 2024 18:15:16 EDT (-0400)
  Re: Compiling POV-Ray 3.7 for Linux  
From: Jim Holsenback
Date: 26 Oct 2011 09:47:41
Message: <4ea80f7d$1@news.povray.org>

> Hi(gh)!
>
> On 26.10.2011 12:04, clipka wrote:
>
>> tar -xjf povray-3.7.0.RC3.tar.bz2
>
> This worked... but then the next problem: after ./configure

>
> I got this:
>
> This is an unofficial version compiled by:

> The POV-Ray Team(tm) is not responsible for supporting this version.
>
> Environment
> -----------
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> /bin/bash: /media/disk1part12/Software: No such file or directory
> configure: WARNING: `missing' script is too old or missing
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking whether $C_INCLUDE_PATH contains the "." path... no
> checking whether $CPLUS_INCLUDE_PATH contains the "." path... no
>
> Programs
> --------
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for stdlib.h... (cached) yes
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking whether the g++ compiler works... yes
> checking how to run the C++ preprocessor... g++ -E
> checking for C++ compiler vendor... gnu
> checking for g++ version... 4.6
> checking for ranlib... ranlib
>
> Libraries
> ---------
> checking whether to link with cygwin DLL... no
> checking whether to enable static linking... no
> checking for the pthreads library -lpthreads... no
> checking whether pthreads work without any flags... no
> checking whether pthreads work with -Kthread... no
> checking whether pthreads work with -kthread... no
> checking for the pthreads library -llthread... no
> checking whether pthreads work with -pthread... yes
> checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
> checking if more special flags are required for pthreads... no
> checking for boostlib >= 1.37... configure: error: We could not detect
> the boost libraries (version 1.37 or higher). If you have a staged boost
> library (still not installed) please specify $BOOST_ROOT in your
> environment and do not give a PATH to --with-boost option. If you are
> sure you have boost installed, then check your version number looking in
> <boost/version.hpp>. See http://randspringer.de/boost for more
> documentation.
>
> All Greek to me! Really, it is the very first time in my life that I try
> to compile larger things than just a single-script C++ program...
> Are there packages missing? Should I install the boost libraries? What
> are boost libraries?
>
> See you in Khyberspace!
>
> Yadgar
>

have a look at the files INSTALL and README in the root of your build 
directory ... tis all spelled out for ya!


Post a reply to this message

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