Hi(gh)!

I just downloaded the zip package from povray.org, unzipped it into my 
home directory... changed to the "unix" directory, read the instructions 
in install.txt - but even failed to perform only the first command, 
./configure COMPILED_BY="Jörg 'Yadgar' Bleimann <yaz### [at] gmxde>", as 
there is no configure program at all!

Where do I have to look?!?

See you in Khyberspace!

Yadgar

Post a reply to this message

Jörg 'Yadgar' Bleimann wrote:

> Hi(gh)!
> 
> I just downloaded the zip package from povray.org, unzipped it into my
> home directory... changed to the "unix" directory, read the instructions
> in install.txt - but even failed to perform only the first command,
> ./configure COMPILED_BY="Jörg 'Yadgar' Bleimann <yaz### [at] gmxde>", as
> there is no configure program at all!
> 
> Where do I have to look?!?
> 
In povray.unix
I dropped a script there to configure/compile/install povray on suse linux.
You should be able to convert it to what you want.
-- 

Ger

Post a reply to this message

Am 07.02.2014 01:15, schrieb Jörg 'Yadgar' Bleimann:
> Hi(gh)!
>
> I just downloaded the zip package from povray.org, unzipped it into my
> home directory... changed to the "unix" directory, read the instructions
> in install.txt - but even failed to perform only the first command,
> ../configure COMPILED_BY="Jörg 'Yadgar' Bleimann <yaz### [at] gmxde>", as
> there is no configure program at all!
>
> Where do I have to look?!?

Note that the zip package is /not/ a Unix source code package, but a 
generic platform-independent one; as such it does not conform to the 
typical unixoid conventions.

In order to turn the generic source code package into a Unix-specific 
one, you'll have to run "prebuild.sh" from the "./unix" directory.

Among other things, this will create the "./configure" script in the 
main directory, which then in turn generates the files needed by "make".

Post a reply to this message

Hi(gh)!

On 07.02.2014 05:48, clipka wrote:

> In order to turn the generic source code package into a Unix-specific
> one, you'll have to run "prebuild.sh" from the "./unix" directory.

...which lead to an error message:
error: requires autoconf 2.59 or above

When trying to install autoconf via apt-get, I discovered that the 
Debian repositories only keep the 2.13 version! And now?

See you in Khyberspace!

Yadgar

Now playing: Cover Me (Bruce Springsteen)

Post a reply to this message

On 02/07/2014 07:48 PM, Jörg 'Yadgar' Bleimann wrote:
> Hi(gh)!
>
> On 07.02.2014 05:48, clipka wrote:
>
>> In order to turn the generic source code package into a Unix-specific
>> one, you'll have to run "prebuild.sh" from the "./unix" directory.
>
> ...which lead to an error message:
> error: requires autoconf 2.59 or above
>
> When trying to install autoconf via apt-get, I discovered that the
> Debian repositories only keep the 2.13 version! And now?

http://www.gnu.org/software/autoconf/#downloading

Post a reply to this message

On 02/07/2014 07:48 PM, Jörg 'Yadgar' Bleimann wrote:
> Hi(gh)!
>
> On 07.02.2014 05:48, clipka wrote:
>
>> In order to turn the generic source code package into a Unix-specific
>> one, you'll have to run "prebuild.sh" from the "./unix" directory.
>
> ...which lead to an error message:
> error: requires autoconf 2.59 or above
>
> When trying to install autoconf via apt-get, I discovered that the
> Debian repositories only keep the 2.13 version! And now?

or try ...

apt-cache search autoconf

i see:
autoconf - automatic configure script builder
autoconf-doc - automatic configure script builder documentation
autoconf2.13 - automatic configure script builder (obsolete version)
autoconf2.64 - automatic configure script builder (obsolete version)
autotools-dev - Update infrastructure for config.{guess,sub} files
autoconf-archive - Autoconf Macro Archive
autoconf-gl-macros - autoconf macros to check for OpenGL/GLU/GLUT
autoconf2.59 - automatic configure script builder (obsolete version)

Post a reply to this message

Hi(gh)!

On 07.02.2014 05:48, clipka wrote:

> In order to turn the generic source code package into a Unix-specific
> one, you'll have to run "prebuild.sh" from the "./unix" directory.
>
> Among other things, this will create the "./configure" script in the
> main directory, which then in turn generates the files needed by "make".

O.k., now I managed to install an autoconf version higher than 2.59 (and 
also automake) just to be able to do prebuild.sh... then I started 
./configure - and now it complains about the missing boost libraries! 
Which packages exactly do I have to install now?

See you in Khyberspace!

Yadgar

Post a reply to this message

On 02/08/2014 12:03 PM, Jörg 'Yadgar' Bleimann wrote:
> Hi(gh)!
>
> On 07.02.2014 05:48, clipka wrote:
>
>> In order to turn the generic source code package into a Unix-specific
>> one, you'll have to run "prebuild.sh" from the "./unix" directory.
>>
>> Among other things, this will create the "./configure" script in the
>> main directory, which then in turn generates the files needed by "make".
>
> O.k., now I managed to install an autoconf version higher than 2.59 (and
> also automake) just to be able to do prebuild.sh... then I started
> ./configure - and now it complains about the missing boost libraries!
> Which packages exactly do I have to install now?

apt-get build-dep libboost-all-dev
apt-get install libboost-all-dev

Post a reply to this message

Hi(gh)!

On 08.02.2014 18:46, James Holsenback wrote:

> apt-get build-dep libboost-all-dev
> apt-get install libboost-all-dev

I did that - and got the error message as follows:

checking whether the Boost::Thread library is available... no
configure: error: cannot find a suitable boost thread library

Where do I get that "thread library"?

See you in Khyberspace!

Yadgar

Post a reply to this message

On 02/08/2014 02:20 PM, Jörg 'Yadgar' Bleimann wrote:
> Hi(gh)!
>
> On 08.02.2014 18:46, James Holsenback wrote:
>
>> apt-get build-dep libboost-all-dev
>> apt-get install libboost-all-dev
>
> I did that - and got the error message as follows:
>
> checking whether the Boost::Thread library is available... no
> configure: error: cannot find a suitable boost thread library
>
> Where do I get that "thread library"?

did you use sudo on apt-get commands?

what does you configure command looks like ... did you add appropriate 
options? http://wiki.povray.org/content/User:Le_Forgeron/vault/Compilation

Post a reply to this message

=?ISO-8859-1?Q?J=F6rg_=27Yadgar=27_Bleimann?= <yaz### [at] gmxde> wrote:
> Hi(gh)!
>
> I just downloaded the zip package from povray.org, unzipped it into my
> home directory... changed to the "unix" directory, read the instructions
> in install.txt - but even failed to perform only the first command,
> ./configure COMPILED_BY="Jörg 'Yadgar' Bleimann <yaz### [at] gmxde>", as
> there is no configure program at all!
>
> Where do I have to look?!?
>
> See you in Khyberspace!
>
> Yadgar

Check the unix section. There are several threads regarding compiling on various
Unix-like system.s

Post a reply to this message

Hi(gh)!

On 09.02.2014 02:34, James Holsenback wrote:

> did you use sudo on apt-get commands?

Not sudo, but generally as su!

> what does you configure command looks like ... did you add appropriate
> options? http://wiki.povray.org/content/User:Le_Forgeron/vault/Compilation

I tried Jerômes version for Ubuntu 13.04, g++ version 4.7.3 and got this:

checking whether the Boost::Thread library is available... no
configure: error: cannot find a suitable boost thread library

- same as before.

The version for Ubuntu 13.10, g++ version 4.8.1:

checking whether the C compiler works... no
configure: error: in `/home/yadgar/povray-3.7-stable':
configure: error: C compiler cannot create executables
See `config.log' for more details

Why is this all so [beeeeep!] complicated?!? I'm about to contemplate 
whether I should change to a 64-bit Windows XP system rather than 
Linux... but I do not want to be online under Windows!!! And my wohnklo 
(German colloquial for "tiny little apartment") is too small for two big 
desktops!

See you in Khyberspace!

Yadgar

Post a reply to this message

On 02/09/2014 08:06 AM, Jörg 'Yadgar' Bleimann wrote:
> Hi(gh)!
>
> On 09.02.2014 02:34, James Holsenback wrote:
>
>> did you use sudo on apt-get commands?
>
> Not sudo, but generally as su!
>
>> what does you configure command looks like ... did you add appropriate
>> options?
>> http://wiki.povray.org/content/User:Le_Forgeron/vault/Compilation
>
> I tried Jerômes version for Ubuntu 13.04, g++ version 4.7.3 and got this:
>
> checking whether the Boost::Thread library is available... no
> configure: error: cannot find a suitable boost thread library
>
> - same as before.
>
> The version for Ubuntu 13.10, g++ version 4.8.1:
>
> checking whether the C compiler works... no
> configure: error: in `/home/yadgar/povray-3.7-stable':
> configure: error: C compiler cannot create executables
> See `config.log' for more details

well geee whizzzz the above tells me you don't even have the correct 
build environment yet ... you need to get the compiler working first.

apt-cache search build-essential

also of interest (povray basic requirements):
apt-get install zlib1g-dev libpng12-dev libjpeg-dev libtiff5-dev

optional:

apt-get install libopenexr-dev
apt-get build-dep libsdl1.2-dev
apt-get install libsdl1.2-dev

> Why is this all so [beeeeep!] complicated?!? I'm about to contemplate
> whether I should change to a 64-bit Windows XP system rather than
> Linux... but I do not want to be online under Windows!!! And my wohnklo
> (German colloquial for "tiny little apartment") is too small for two big
> desktops!

No it's not really complicated ... just new to you. If you're not 
willing to dig in and learn it, maybe switching is the right answer, but 
hey IMHO building binaries on windows machines is WAY more involved.

Post a reply to this message

=?ISO-8859-1?Q?J=F6rg_=27Yadgar=27_Bleimann?= <yaz### [at] gmxde> wrote:

Well, let's start at the beginning:

1) What kind of computer are you running?
2) What OS are you using? (Debina? Ubuntu? Mint? SteamOS?)
3) If all else fails, I or someone else can compile a static binary and send it
to you.

With regard to boost, I have not had any problems with downloading, compiling,
and installing the boost libraries from www.boost.org (actually only need to
compile two of the threading libraries, but I install all of it anyway).

Post a reply to this message

On 02/09/2014 02:06 PM, Jörg 'Yadgar' Bleimann a dit:

> Why is this all so [beeeeep!] complicated?!?

    Because having a working boost is a moving target ?

-- 
http://foo.bar.quux.over-blog.com/article-thsf-2013-114632120.html

Post a reply to this message

Have you been using Povray 3.6 this whole time? Were you able to compile any of
the 3.7RCs during the past year?

Post a reply to this message

On 02/09/2014 10:07 AM, jhu wrote:
> =?ISO-8859-1?Q?J=F6rg_=27Yadgar=27_Bleimann?= <yaz### [at] gmxde> wrote:
>
> Well, let's start at the beginning:
>
> 1) What kind of computer are you running?
> 2) What OS are you using? (Debina? Ubuntu? Mint? SteamOS?)

look at his last post ;-)

Post a reply to this message

James Holsenback <nom### [at] nonecom> wrote:
> On 02/09/2014 10:07 AM, jhu wrote:
> > =?ISO-8859-1?Q?J=F6rg_=27Yadgar=27_Bleimann?= <yaz### [at] gmxde> wrote:
> >
> > Well, let's start at the beginning:
> >
> > 1) What kind of computer are you running?
> > 2) What OS are you using? (Debina? Ubuntu? Mint? SteamOS?)
>
> look at his last post ;-)

Doesn't say what OS he's using. He just says he tried instructions for Ubuntu
13.10 and 13.04. That doesn't tell us what OS he's actually using. Assuming apt
works on his system, he could be running any Debian-based OS (Debian, Ubunt,
Mint, SteamOS, etc.).

Post a reply to this message

On 02/09/2014 11:42 AM, jhu wrote:
> James Holsenback <nom### [at] nonecom> wrote:
>> On 02/09/2014 10:07 AM, jhu wrote:
>>> =?ISO-8859-1?Q?J=F6rg_=27Yadgar=27_Bleimann?= <yaz### [at] gmxde> wrote:
>>>
>>> Well, let's start at the beginning:
>>>
>>> 1) What kind of computer are you running?
>>> 2) What OS are you using? (Debina? Ubuntu? Mint? SteamOS?)
>>
>> look at his last post ;-)
>
> Doesn't say what OS he's using. He just says he tried instructions for Ubuntu
> 13.10 and 13.04. That doesn't tell us what OS he's actually using. Assuming apt
> works on his system, he could be running any Debian-based OS (Debian, Ubunt,
> Mint, SteamOS, etc.).
>
>

lol ... only after posting did I consider that I'd made too big of an 
assumption

Post a reply to this message

Hi(gh)!

On 09.02.2014 15:51, James Holsenback wrote:

> apt-cache search build-essential

sbuild - Tool for building Debian binary packages from Debian sources
build-essential - Informal list of packages needed to generate packages
devscripts - Scripts to make the life of a Debian package attendant easier
dh-buildinfo - debhelper enhancement to track package versions used in 
building of a package

Is that enough?

> also of interest (povray basic requirements):
> apt-get install zlib1g-dev libpng12-dev libjpeg-dev libtiff5-dev

Note: »libjpeg62-dev« chosen instead of »libjpeg-dev«
Error: Package libtiff5-dev cannot be found.

> apt-get install libopenexr-dev

Error: Package libopenexr-dev cannot be found.

> apt-get build-dep libsdl1.2-dev

The following packages have unresolved dependences:
libaa1-dev : depends on: libslang2-dev but shall not be installed
               depends on: libncurses5-dev but shall not be installed
  libarts1-dev : depends on: libartsc0-dev (= 1.5.9-3+b2) but shall not 
be installed
                 depends on: libglib2.0-dev but shall not be installed
                 depends on: libjack0.100.0-dev
                 depends on: libmad0-dev but shall not be installed
                 depends on: libogg-dev but shall not be installed
                 depends on: libqt3-mt-dev (>= 3:3.3.5) but shall not be 
installed
                 depends on: libvorbis-dev but shall not be installed
  libasound2-dev : depends on: libasound2 (= 1.0.23-2.1)
  libcaca-dev : depends on: libcaca0 (= 0.99.beta17-1) but 0.99.beta18-1 
shall be installed
                depends on: libncurses5-dev but shall not be installed
                depends on: libslang2-dev but shall not be installed
  libdirectfb-dev : depends on: libdirectfb-1.2-9 (= 1.2.10.0-4) but 
1.2.10.0-5 shall be installed
                    depends on: libdirectfb-extra but shall not be installed
                    depends on: libfreetype6-dev but shall not be installed
                    depends on: libjpeg-dev
                    depends on: libpng12-dev but shall not be installed
                    depends on: zlib1g-dev (>= 1:1.1.3) soll aber nicht 
installiert werden
                    depends on: libsysfs-dev but shall not be installed
  libesd0-dev : depends on: libesd0 (= 0.2.41-8) but 0.2.41-10+b1 shall 
be installed
                depends on: esound-common (= 0.2.41-8) but 0.2.41-10 
shall be installed
  libgl1-mesa-dev : depends on: libgl1-mesa-glx (= 7.7.1-6) but 
8.0.5-4+deb7u2 shall be installed
  libglu1-mesa-dev : depends on: libglu1-mesa (= 7.7.1-6) but 
8.0.5-4+deb7u2 shall be installed
  libpulse-dev : depends on: libpulse0 (= 0.9.21-3+squeeze1) but 2.0-6.1 
shall be installed
                 depends on: libpulse-mainloop-glib0 (= 
0.9.21-3+squeeze1) but 2.0-6.1 shall be installed
                 depends on: libpulse-browse0 (= 0.9.21-3+squeeze1) but 
shall not be installed
                 depends on: libglib2.0-dev but shall not be installed
                 depends on: libavahi-client-dev but shall not be installed
  libsvga1-dev : depends on: libsvga1 (= 1:1.4.3-29) but 1:1.4.3-33 
shall be installed
  libx11-dev : depends on: libx11-6 (= 2:1.3.3-4+squeeze1) but 
2:1.5.0-1+deb7u1 shall be installed
               depends on: libxau-dev (>= 1:1.0.0-1) but shall not be 
installed
               depends on: libxdmcp-dev (>= 1:1.0.0-1) but shall not be 
installed
               depends on: libxcb1-dev but shall not be installed
  libxext-dev : depends on: libxext6 (= 2:1.1.2-1+squeeze1) but 
2:1.3.1-2+deb7u1 shall be installed
                depends on: x11proto-xext-dev (>= 7.0.99.2) but shall 
not be installed
  libxt-dev : depends on: libxt6 (= 1:1.0.7-1+squeeze1) but 
1:1.1.3-1+deb7u1 shall be installed
              depends on: libsm-dev soll aber nicht installiert werden
  libxv-dev : depends on: libxv1 (= 2:1.0.5-1+squeeze1) but 
2:1.0.7-1+deb7u1 shall be installed
Error: Build dependences for libsdl1.2-dev could not be resolved.

> apt-get install libsdl1.2-dev

The following packages have unresolved dependences:
  libsdl1.2-dev : Depends on: libsdl1.2debian (= 1.2.14-6.1) but 
1.2.15-5 shall be installed
                  Depends on: libx11-dev shall not be installed
                  Depends on: libglu1-mesa-dev shall not be installed
                  Depends on: libasound2-dev shall not be installed
                  Depends on: libartsc0-dev shall not be installed
                  Depends on: libesd0-dev shall not be installed
                  Depends on: libpulse-dev shall not be installed
                  Depends on: libdirectfb-dev (>= 0.9.22) shall not be 
installed
                  Depends on: libsvga1-dev shall not be installed
                  Depends on: libaa1-dev shall not be installed
                  Depends on: libcaca-dev shall not be installed
                  Depends on: libxt-dev shall not be installed
                  Depends on: libxext-dev shall not be installed
Error: Problems cannot be corrected, you have defect packages held back.

I'm fed up with it... Linux sucks!!!

I give up! Linux sucks!

> No it's not really complicated ... just new to you. If you're not
> willing to dig in and learn it, maybe switching is the right answer, but
> hey IMHO building binaries on windows machines is WAY more involved.

I want my Commodore 64 back!

See you in Khyberspace!

Yadgar

Post a reply to this message

Hi(gh)!

On 09.02.2014 16:07, jhu wrote:

> 1) What kind of computer are you running?

A hexacore AMD Phenom.

> 2) What OS are you using? (Debina? Ubuntu? Mint? SteamOS?)

Debian stable 6.0.5.

> 3) If all else fails, I or someone else can compile a static binary and send it
> to you.

O.k....

> With regard to boost, I have not had any problems with downloading, compiling,
> and installing the boost libraries from www.boost.org (actually only need to
> compile two of the threading libraries, but I install all of it anyway).

When I tried to install 3.7 RC3 back in 2011, I did this - and wrecked 
my entire system! Please not again!

See you in Khyberspace!

Yadgar

Post a reply to this message

Hi(gh)!

On 09.02.2014 16:12, jhu wrote:
> Have you been using Povray 3.6 this whole time?

Yes, I did.

> Were you able to compile any of
> the 3.7RCs during the past year?

No, I wasn't.

See you in Khyberspace!

Yadgar

Post a reply to this message

On 02/09/2014 06:04 PM, Jörg 'Yadgar' Bleimann wrote:
> I'm fed up with it... Linux sucks!!!
>
> I give up! Linux sucks!

LOL ... should have seen this coming a mile away.

Post a reply to this message

=?ISO-8859-1?Q?J=F6rg_=27Yadgar=27_Bleimann?= <yaz### [at] gmxde> wrote:
> Hi(gh)!
>
> On 09.02.2014 16:07, jhu wrote:
>
> > 1) What kind of computer are you running?
>
> A hexacore AMD Phenom.
>
> > 2) What OS are you using? (Debina? Ubuntu? Mint? SteamOS?)
>
> Debian stable 6.0.5.
>
> > 3) If all else fails, I or someone else can compile a static binary and send it
> > to you.
>
> O.k....
>

> Yadgar

Check http://news.povray.org/povray.binaries.misc/ in a few minutes. A static
binary for povray should show up momentarily.

Post a reply to this message

Oops! The last one I posted was compiled for Ivy Bridge. I posted a new one
compiled for Phenom. It should run faster. Again, it' in the binary/misc area.

Post a reply to this message

Hi(gh)!

On 10.02.2014 06:19, jhu wrote:
> Oops! The last one I posted was compiled for Ivy Bridge. I posted a new one
> compiled for Phenom. It should run faster. Again, it' in the binary/misc area.

I downloaded it, but I couldn't open it, neither with Ark nor with 
another archive manager - it simply seems to contain nothing at all!

Perhaps I'm just to stupid for raytracing, I should content myself with 
drinking beer and watching TV, like all the other rednecks...

See you in Huntsville, Alabama!

Yadgar

Post a reply to this message

On 02/10/2014 07:48 AM, Jörg 'Yadgar' Bleimann wrote:
> Hi(gh)!
>
> On 10.02.2014 06:19, jhu wrote:
>> Oops! The last one I posted was compiled for Ivy Bridge. I posted a
>> new one
>> compiled for Phenom. It should run faster. Again, it' in the
>> binary/misc area.
>
> I downloaded it, but I couldn't open it, neither with Ark nor with
> another archive manager - it simply seems to contain nothing at all!

both archives downloaded and extracted fine on my end ... perhaps bz2 
format isn't supported. I'm using ark as well and IIRC bz2 support was 
/not/ part of the standard install

>
> Perhaps I'm just to stupid for raytracing, I should content myself with
> drinking beer and watching TV, like all the other rednecks...
>
> See you in Huntsville, Alabama!

trust me ... Huntsville Alabama is /not/ the redneck capital world. Oh 
and BTW: ... it's moonshine not beer

Post a reply to this message

=?ISO-8859-1?Q?J=F6rg_=27Yadgar=27_Bleimann?= <yaz### [at] gmxde> wrote:
> Hi(gh)!
>
> On 10.02.2014 06:19, jhu wrote:
> > Oops! The last one I posted was compiled for Ivy Bridge. I posted a new one
> > compiled for Phenom. It should run faster. Again, it' in the binary/misc area.
>
> I downloaded it, but I couldn't open it, neither with Ark nor with
> another archive manager - it simply seems to contain nothing at all!
>
> Perhaps I'm just to stupid for raytracing, I should content myself with
> drinking beer and watching TV, like all the other rednecks...
>
> See you in Huntsville, Alabama!
>
> Yadgar

apt-get install bzip2

Post a reply to this message

ok, uploaded a gzipped version. Check again.

Post a reply to this message

Well, this is silly. Looks like the file gets zipped or gzipped or something
when it's uploaded (even though I've already gzipped it!!!) so you'll need to
double gunzip it as follows:

cat povray.barcelona.gz | gunzip | gunzip > povray

Post a reply to this message

Hi(gh)!

On 10.02.2014 15:11, jhu wrote:

> apt-get install bzip2

apt says bzip2 is already installed!

See you in Khyberspace!

Yadgar

Post a reply to this message

Hi(gh)!

On 10.02.2014 15:31, jhu wrote:

> cat povray.barcelona.gz | gunzip | gunzip > povray

That (respectively doing it with Ark) worked generally... but obviously, 
you included only the bare executable, so povray does not find any 
configuration file, neither system-wide nor user specific! Can I use 
POV-Ray 3.6's configuration file (at least for the time being)?

See you in Khyberspace!

Yadgar

Post a reply to this message

=?ISO-8859-1?Q?J=F6rg_=27Yadgar=27_Bleimann?= <yaz### [at] gmxde> wrote:
> Hi(gh)!
>
> On 10.02.2014 15:31, jhu wrote:
>
> > cat povray.barcelona.gz | gunzip | gunzip > povray
>
> That (respectively doing it with Ark) worked generally... but obviously,
> you included only the bare executable, so povray does not find any
> configuration file, neither system-wide nor user specific! Can I use
> POV-Ray 3.6's configuration file (at least for the time being)?
>
> See you in Khyberspace!
>
> Yadgar

From the main povray source you downloaded, copy the following directories to
/usr/local/share/povray-3.7

ini
include
scenes
scripts

The only thing that's really neceasary is what's in the include directory.

Post a reply to this message

Hi(gh)!

On 10.02.2014 17:21, jhu wrote:

>  From the main povray source you downloaded, copy the following directories to
> /usr/local/share/povray-3.7
>
> ini
> include
> scenes
> scripts

After having also copied povray.conf and povray.ini into the respective 
(newly created) directories, it works fine... thank you for compiling, jhu!

Two issues remain: firstly, I still get a warning message "Problem with 
option setting", and, as already with 3.6 on my Linux system, I have no 
proper preview window, instead of displaying the scene, merely the 
non-white parts of backdrop (non-POV-Ray) windows are tinted. I assume 
that this is a problem of my graphics driver... do you know of any 
workarounds for this (in earlier installations of Debian Linux, I in 
fact had a real rendering preview!)?

See you in Khyberspace!

Yadgar

Now playing: To Germany With Love (Alphaville)

Post a reply to this message

=?ISO-8859-1?Q?J=F6rg_=27Yadgar=27_Bleimann?= <yaz### [at] gmxde> wrote:
> Hi(gh)!
>
> On 10.02.2014 17:21, jhu wrote:
>
> >  From the main povray source you downloaded, copy the following directories to
> > /usr/local/share/povray-3.7
> >
> > ini
> > include
> > scenes
> > scripts
>
> After having also copied povray.conf and povray.ini into the respective
> (newly created) directories, it works fine... thank you for compiling, jhu!
>
> Two issues remain: firstly, I still get a warning message "Problem with
> option setting", and, as already with 3.6 on my Linux system, I have no
> proper preview window, instead of displaying the scene, merely the
> non-white parts of backdrop (non-POV-Ray) windows are tinted. I assume
> that this is a problem of my graphics driver... do you know of any
> workarounds for this (in earlier installations of Debian Linux, I in
> fact had a real rendering preview!)?
>
> See you in Khyberspace!
>
> Yadgar
>
> Now playing: To Germany With Love (Alphaville)

Glad it works now! With regard to preview window, I don't know. It's not
something I've noticed mainly because I'm usually rendering on headless
computers.

Post a reply to this message

On 02/11/2014 07:07 PM, Jörg 'Yadgar' Bleimann wrote:
> Hi(gh)!
>
> On 10.02.2014 17:21, jhu wrote:
>
>>  From the main povray source you downloaded, copy the following
>> directories to
>> /usr/local/share/povray-3.7
>>
>> ini
>> include
>> scenes
>> scripts
>
> After having also copied povray.conf and povray.ini into the respective
> (newly created) directories, it works fine... thank you for compiling, jhu!
>
> Two issues remain: firstly, I still get a warning message "Problem with
> option setting", and, as already with 3.6 on my Linux system, I have no
> proper preview window, instead of displaying the scene, merely the
> non-white parts of backdrop (non-POV-Ray) windows are tinted. I assume
> that this is a problem of my graphics driver... do you know of any
> workarounds for this (in earlier installations of Debian Linux, I in
> fact had a real rendering preview!)?

in regards to the lack of preview window, perhaps the binary was built 
without libsdl (simple directmedia layer) ... see what povray --version 
returns (hint look for X Window display enabled/disabled)

Post a reply to this message

"jhu" <nomail@nomail> wrote:

>
> Glad it works now! With regard to preview window, I don't know. It's not
> something I've noticed mainly because I'm usually rendering on headless
> computers.

Looks like it's compiled with X window disabled. That's probably why there's no
preview window. Let me see if I can enable X window support...

Post a reply to this message

On 12/02/14 00:10, jhu wrote:
> 
> Glad it works now! With regard to preview window, I don't know. It's not
> something I've noticed mainly because I'm usually rendering on headless
> computers.
> 

IIRC I used to have to run 3.6 with the option -visual DirectColor. I
put an alias in my ~/.bashrc thus:
alias povray=povray\ -visual\ DirectColor

I haven't had to do this for 3.7. But it might be worth trying it.
BTW Are you running Gnome or KDE? What version?

John
-- 
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children

Post a reply to this message

Oops. I posted at the same time as jhu and Jim. They seem to have the
solution. I hadn't thought that jhu might have compiled with the display
disabled.

John
-- 
Protect the Earth
It was not given to you by your parents
You hold it in trust for your children

Post a reply to this message

"jhu" <nomail@nomail> wrote:
> "jhu" <nomail@nomail> wrote:
>
> >
> > Glad it works now! With regard to preview window, I don't know. It's not
> > something I've noticed mainly because I'm usually rendering on headless
> > computers.
>
> Looks like it's compiled with X window disabled. That's probably why there's no
> preview window. Let me see if I can enable X window support...

Unfortunately, not able to compile a static binary with X Window support.
Incidentally, I can compile a dynamic binary with X Window support, but that is
unlikely to work on your system since I'm compiling on Ubuntu 12.04.

Post a reply to this message

HI(gh)!

On 12.02.2014 01:10, jhu wrote:

> Glad it works now! With regard to preview window, I don't know. It's not
> something I've noticed mainly because I'm usually rendering on headless
> computers.

No monitor at all? Blind POVing... fascinating!

See you in Khyberspace!

Yadgar

Post a reply to this message

On 02/12/2014 03:33 PM, Jörg 'Yadgar' Bleimann a dit:

> No monitor at all? Blind POVing... fascinating!

   Not fascinating. Just efficiency.

-- 
http://foo.bar.quux.over-blog.com/article-annlor-fait-des-bulles-121970031.html

Post a reply to this message

Posted a new binary in misc section. It should be 8% faster the current one you
have. But don't take my word for it. Try testing it via the benchmark.

Post a reply to this message