Hi(gh)!

On 26.10.2011 00:32, clipka wrote:

> That should be a *.tar.bz2 file actually. You won't get far with the
> Windows zip file on a Linux machine :-P

In fact it is! But I'm not even able to unpack the archive with ark 
correctly - all I get is an error message saying "libarchive is not able 
to process the archive file"!

See you in Khyberspace!

Yadgar

Post a reply to this message

Compare with this scene I happen to work on at this moment and rendered 
with version 3.7...

Thomas

Post a reply to this message

Attachments:
Download 'at the jackal_03.png' (683 KB)

Preview of image 'at the jackal_03.png'

> Hi(gh)!
>
> On 26.10.2011 00:32, clipka wrote:
>
>> That should be a *.tar.bz2 file actually. You won't get far with the
>> Windows zip file on a Linux machine :-P
>
> In fact it is! But I'm not even able to unpack the archive with ark
> correctly - all I get is an error message saying "libarchive is not able
> to process the archive file"!

I don't know that "ark" you're mentioning; do you mean arc? arj? ar? 
 From what I know, each of these three is specialized on one special 
type of compressed file respectively, none of which is the bzip2 format.

The traditional official way to extract the contents should be:

     bunzip2 povray-3.7.0.RC3.tar.bz2
     tar -xf povray-3.7.0.RC3.tar

The following single command should also do the job:

     tar -xjf povray-3.7.0.RC3.tar.bz2

Post a reply to this message

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

Post a reply to this message

> 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

High!

On 26.10.2011 15:47, Jim Holsenback wrote:

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

In fact I did nothing else but reading through INSTALL.txt - 
http://www.povray.org/beta/source/unix-src-INSTALL.txt !

See you in Khyberspace!

Yadgar

Post a reply to this message

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

Boost libraries := something you should install; check out your Linux 
distribution's package manager, it'll most likely have them. Make sure 
to also install the "developer" package for the boost libraries 
(probably named something like "boost-dev" or "boost-devel").

If you still experience problems even after installing the boost 
libraries, try adding the command-line option 
"--with-boost-thread=boost_thread-mt" to ./configure.

Post a reply to this message

High!

On 26.10.2011 22:55, clipka wrote:

> Boost libraries := something you should install; check out your Linux
> distribution's package manager, it'll most likely have them. Make sure
> to also install the "developer" package for the boost libraries
> (probably named something like "boost-dev" or "boost-devel").

But I did not know which boost packages exactly are necessary, I 
foolishly tried apt-get install boost* - which totally blew my system, 
the system partition ran full, and nothing worked anymore...

Meanwhile, I have mostly recovered from the crash - but I still do not 
now which boost packages to install...

See you in Khyberspace!

Yadgar

Now playing: Rio (Duran Duran)

Post a reply to this message

Hi(gh)!

On 25.10.2011 22:07, clipka wrote:

> What you really should try is POV-Ray 3.7 - radiosity has changed a lot
> since 3.6.

During the prolonged weekend, I stayed with a friend who in fact runs 
3.7 on his multi-processor systems - and even though I decreased count 
to 100 and upped error_bound to 0.15, the result (attached here) was 
much more satisfying than everything I achieved under 3.6!

See you in Khyberspace!

Yadgar

Now playing: September Gurls (Bangles)

Post a reply to this message

Attachments:
Download '2011-10-30 port whatmough residential building #1, take 195 - view from kitchen into atelier, modified andresdottir radi' (19 KB)

Preview of image '2011-10-30 port whatmough residential building #1, take 195 - view from kitchen into atelier, modified andresdottir radi'

> Hi(gh)!
>
> On 25.10.2011 22:07, clipka wrote:
>
>> What you really should try is POV-Ray 3.7 - radiosity has changed a lot
>> since 3.6.
>
> During the prolonged weekend, I stayed with a friend who in fact runs
> 3.7 on his multi-processor systems - and even though I decreased count
> to 100 and upped error_bound to 0.15, the result (attached here) was
> much more satisfying than everything I achieved under 3.6!

Now what did I tell you? :-)

Post a reply to this message