|
|
|
|
|
|
| |
| |
|
|
From: Warp
Subject: -benchmark not working for a local installation
Date: 28 Jul 2012 02:01:11
Message: <50138027@news.povray.org>
|
|
|
| |
| |
|
|
After upgrading my entire system (OpenSuse 12.1) I compiled povray for it
and tried to run it with -benchmark. I only installed povray locally in my
home directory. It could not find "functions.inc". (It can find it when
running anything else.)
The message given by povray when running it with that parameter is that
it will look for +L parameters in the command line, so I specified one
to point to the standard include file directory. It still could not find
"functions.inc". The exact command I used was this:
povray +L/home/warp/software/povray-3.7.0.RC6/include -benchmark
The only way I was able to make it work was to actually go to that directory
and run it directly from there. Then it was able to find it.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp <war### [at] tagpovrayorg> wrote:
> After upgrading my entire system (OpenSuse 12.1) I compiled povray for it
> and tried to run it with -benchmark. I only installed povray locally in my
> home directory. It could not find "functions.inc". (It can find it when
> running anything else.)
>
> The message given by povray when running it with that parameter is that
> it will look for +L parameters in the command line, so I specified one
> to point to the standard include file directory. It still could not find
> "functions.inc". The exact command I used was this:
>
> povray +L/home/warp/software/povray-3.7.0.RC6/include -benchmark
>
> The only way I was able to make it work was to actually go to that directory
> and run it directly from there. Then it was able to find it.
It works under Linux Mint so I think it has to do with OpenSuse's security
enhancements that made me switch linux version. I just freaked out with all the
special files that needed to change every time I wanted to do something that I
had done in Ubuntu earlier without effort.
Have fun raytracing.
Post a reply to this message
|
|
| |
| |
|
|
From: Warp
Subject: Re: -benchmark not working for a local installation
Date: 14 Sep 2012 03:06:59
Message: <5052d793@news.povray.org>
|
|
|
| |
| |
|
|
"Mikael ?hlin" <mic### [at] onsdagorg> wrote:
> It works under Linux Mint so I think it has to do with OpenSuse's security
> enhancements that made me switch linux version.
That doesn't make any sense. How exactly is OpenSuse stopping povray from
reading a file *in my home directory* specified with the +L parameter?
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
From: Le Forgeron
Subject: Re: -benchmark not working for a local installation
Date: 14 Sep 2012 09:48:01
Message: <50533591$1@news.povray.org>
|
|
|
| |
| |
|
|
Le 14/09/2012 09:06, Warp a écrit :
> "Mikael ?hlin" <mic### [at] onsdagorg> wrote:
>> It works under Linux Mint so I think it has to do with OpenSuse's security
>> enhancements that made me switch linux version.
>
> That doesn't make any sense. How exactly is OpenSuse stopping povray from
> reading a file *in my home directory* specified with the +L parameter?
>
IIRC, -benchmark will use a hard-coded scene, ignoring your
$HOME/.povray settings (to render no file and such), but the issue is
that, unless you have installed the include files at the right place,
the hard-coded file will fails, because it depends on these includes.
The usual trap is:
* untar the tarball
* run configure
* run make
* try ./unix/povray --benchmark
Boomer on a fresh system
(but fine on a system where "make install" was already ran)
In an ideal world, the benchmark would not need a #include, but have
everything needed embedded.
Post a reply to this message
|
|
| |
| |
|
|
From: Warp
Subject: Re: -benchmark not working for a local installation
Date: 15 Sep 2012 07:28:49
Message: <50546671@news.povray.org>
|
|
|
| |
| |
|
|
Le_Forgeron <lef### [at] freefr> wrote:
> In an ideal world, the benchmark would not need a #include, but have
> everything needed embedded.
I think this would be the best solution. After all, it's not like the
benchmark uses a ginormous amount of #included code.
This would make it work completely independently, even if you had the
povray executable and nothing else.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |