> tcsh: povray: Command not found.

	Try the tcsh command 'rehash' and then 'povray' should be found,
assuming the binary is installed in a directory that belongs to your
PATH environment variable.  Check 'printent PATH' for that.

> Whenever I enter the "make check" command I get an error message:
> 
> Scene File Parser Initialization Error: Reading from
> '/povray-3.6.1/scenes/advan
> ced/biscuit.pov' is not permitted.  Check the configuration in
>  '/usr/local/etc/povray/3.6/povray.conf'.

	The 'make check' command is meant to be run only before the
package is installed with 'make install'.   If you run 'make check'
again afterwards, the default settings in the ~/.povray/3.6/povray.conf
file will prevent you reading the demo scene again.  This behaviour is
expected.  The 'make check' command is there only for verifying that
the binary you just compiled is working normally, before you install
all the rest of the scene, include, and related files.

	- NC

Post a reply to this message

> Just to be thorough I did go through the "/var/root/.povray/3.6/povray.conf"
> file and changed the lines
> to
> 
> [File I/O Security]
> none       ; all read and write operations on files are allowed.
> ;read-only  ; uses the "read+write" directories for writing (see below).
> ;restricted  ; uses _only_ "read" and "read+write" directories for file I/O.

> Still, I got the same error mentioned in my previous posting with the "make
> check" command.

	That's odd.
	Please, write the paths where you have installed POV-Ray to.  You just
need to report the content of the /var/root/.povray/3.6/povray.ini file
(the Library_Path entries at the end of the file).
	Also report the full last section of the povray.conf file, i.e.
all read(*) and read-write(*) entries at the end of the file.

	- NC

Post a reply to this message

> PATH environment variable.  Check 'printent PATH' for that.

	Sorry, that's  'printenv PATH'  or simply  'echo $PATH' .
	Also, if you open a new shell and POV-Ray is installed in a standard
directory, you should immediatly be able to use 'povray' without doing the
'rehash' first.

	- NC

Post a reply to this message

Nicolas,

Thanks so much for your suggestions.  If it's not already obvious, I am only
a beginner with unix so your advice pointed me in the right direction to
fix things.  I'll explain what I discovered in the process in the hopes
that it might be of assistance to other unix neophytes with apple osx
computers. :)

The default target directory for the binary install is /usr/local/bin (plus
other folders as explained in the INSTALL document).

On the other hand, my $PATHs are

/bin:/sbin:/usr/bin:/usr/sbin

I have never changed this and it may be a "default" so this may or may not
end up being an issue for other osx users.  [Would it be possible for the
installer to check the $PATH variable and install the binaries based on the
results?]

Rather than change this pathway I used the instructions in the INSTALL doc
to

% ./configure --prefix=/usr/bin COMPILED_BY="chris morgan
<iso### [at] yahoocom>"
% make check install

This seemed to work better because the check worked except that even after
using "rehash" I still got the message:

tcsh: povray: Command not found.

So I looked back through the reporting in the terminal window and found the
files were actually installed in usr/bin/etc as well as usr/bin/bin.

So, next (after uninstalling this version) I left of the /bin and installed
it with

% ./configure --prefix=/usr COMPILED_BY="chris morgan <iso### [at] yahoocom>"
% make check install

and it worked!!!!

Now the only problem remaining is that I didn't note where it installed the
..inc files so in the meantime I just used the "Library_Path=" in my .ini
file to reference the .inc files that were in the installer folder.
thanks again for your help.
chris

Post a reply to this message

> /bin:/sbin:/usr/bin:/usr/sbin

	I don't know what is "standard" in MacOSX, but I'd suggest you to
have a /usr/local/bin in your PATH (before any other) and install all
additional packages, such as POV-Ray, in there.  This has the advantage
to avoid messing up the system.  Moreover I guess this is what is
recommanded by the FHS (filesystem hierarchy standard).

> [Would it be possible for the
> installer to check the $PATH variable and install the binaries based on the
> results?]

	For the reasons above, the answer is "no"  :-)

	In principle you can easily add the /usr/local/bin path in the
default PATH environment, either as root or as non-priviledged user.
In the case of tcsh, you should add  'setenv PATH /usr/local/bin:$PATH'
in either /etc/csh.cshrc or /etc/csh.login (as root) or in ~/.cshrc
~/.login (as user).  Consult the tcsh manual ('man tcsh', in section
"Startup and shutdown") for further details.

> I used the instructions in the INSTALL doc

	Good  ;-)

> % ./configure --prefix=/usr

	If you have /usr/local/bin in your PATH as discussed above, you
will not need to use the --prefix option for any package that uses the
GNU configure scheme (which nowadays is the de facto standard for source
packages).

	- NC

Post a reply to this message

In article <41b5beb6$1@news.povray.org> , Nicolas Calimet 
<pov### [at] freefr>  wrote:

>  I don't know what is "standard" in MacOSX, but I'd suggest you to

/Applications for all Mac OS X applications.  Normal users never see the
command-line. Depending on the Mac OS X version and install options used,
the command-line environment isn't setup ... but don't ask for the defaults
if it is setup, I haven't had to do a clean install ever since I got my
system almost three years ago.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Nicolas, thanks again for the pointers.  After you first introduced me to
$PATH I researched it and actually come across the means of appending the
PATH.  However, my thinking at the time was that it wasn't a good idea for
me because I will eventually need to install this command line version on
15 computers in my lab at school.  I figured I could save a step by
avoiding the need to add /usr/local/bin on each machine.   But now I see it
is better to not fight a standard and so I took your advice and did this on
a second machine by just using the vi editor on the /etc/csh.login document
(I hope that is okay).  And even though the "make check" still didn't work,
povray worked flawlessly and I didn't even have to do anything special to
show it where the include files were.

Thorsten is correct that on the MacOSX systems the root account is disabled
by default in order to prevent users from doing things they shouldn't with
the system files.  On the other hand, the primary user has so-called
"adminstrator" priveledes similar to root including 'sudo' (but not 'su' -
yet, another point that might affect a would-be mac-based user wanting to
install the command-line version since the installer step 3 is "su").
Still, perhaps most people fiddling around with the terminal application in
OSX will have enabled the root account (which is very easy to do).

Finally, I just did a quick search online and discovered that beginning with
OSX 10.2 (we are now in version 10.3) /usr/local/bin is "no longer part of
the default environment variables".  So, this issue will probably end up
being a problem for anyone like me who doesn't really know what they are
doing :).  Should the INSTALL document point this out or does this affect
too few people?
thanks again for all of your help.
chris

ps, since I mentioned it, can I impose on you to suggest any UNIX resources
that deal with installing software on multiple machines across a network?
I have heard of 'shell scripts' before and I am wondering if this is the
direction I need to research.

Post a reply to this message

> Finally, I just did a quick search online and discovered that beginning with
> OSX 10.2 (we are now in version 10.3) /usr/local/bin is "no longer part of
> the default environment variables".

	Is it explained anywhere why such a decision was made?  (In case
it is claimed that it's for "security" reasons, I'd actually expect more
trouble than safety).

> ps, since I mentioned it, can I impose on you to suggest any UNIX resources
> that deal with installing software on multiple machines across a network?

	Sorry I'm not a sysadmin used to install things on many machines
at once.  However, as you will have to log as root on each of them, I'm not
sure it's actually useful to have a script trying to automate this.
	I suppose what is done usually (in the context of a network made of
similar machines) is to have a fileserver that owns all the softwares in a
single location, for instance in the /usr/local directory.  Then this
directory is shared over network via e.g. NFS mounts; i.e. each client
machine mounts the /usr/local directory of the fileserver.  To avoid
slowing down the network, the filesever should be a machine which has
good hardware ressources, which is not likely to be your case.

	Therefore, you may have the only possibility to install POV-Ray
on each machine seperatly.  If all of your machines are running the same
OS version and are accessible from a single one via e.g. SSH, you don't
have to recompile POV-Ray on each machine.  Instead, you can compile and
install it once, then replicate this install on the other machines.

	For instance:

1) compile and install POV-Ray on one machine under the /usr/local
directory you've just created.
2) since /usr/local does contain nothing but POV-Ray files, pack this
directory in a (compressed) tar file called install.tar.gz :

cd /
tar cvf install.tar /usr/local
gzip --best install.tar   (which gives install.tar.gz)

3) copy and unpack this archive on all the other machines

scp install.tar.gz root@the_other_machine:/
ssh -l root the_other_machine
cd /
tar xvzf install.tar.gz

4) adapt the PATH where necessary.

	Note that you may find this procedure actually more time-consuming
than just running configure and compiling the program on each machine (which
of course can be done in parallel, so the compilation time doesn't scale as
the number of machines).

	Again, I don't know whether things can be done in a more automatic
manner, so these are just my not-so-efficient suggestions.

	- NC

Post a reply to this message

Nicolas, thank you very much for your advice and for being so generous with
your time.  Your suggestions have helped a lot.  I was not aware that one
could compress the binaries and just copy them from machine to machine.  I
am still studying your example and it will take me a little time to try
your suggestions since I don't have access to my lab at the moment.  Still,
in the meantime I did try out remotely logging in as root using "ssh
root@<other machine IP>.  so, if I can log onto each machine then I should
be able to change the PATH variables and then move and uncompress the tar
files.  I suppose that in theory I could write a script to do this
automatically but by the time I get that working I could have probably just
gone from machine to machine with a CD of the tar files.  Anyway, I will
write back when I try this out. Thanks again, Chris

Post a reply to this message

Paul Bourke <pdb### [at] swineduau> wrote:
> There has been some discussion here about PovRay 3.6.1
> compiling under Mac OS-X. I can confirm that it does
> compile "out-of-the-box", I just did it as a test. So,
> if it doesn't for you then I imagine you don't have the
> full developer tools installed. If anyone does does want
> the command line version for Mac OS-X then let me know
> and I'll make a binary available.
> --
> Paul Bourke
> pdb_NOSPAMswin.edu.au

Hey Paul--if you read this after so long a time--I was able to compile POV
3.6.1 on my iMac Core Duo, although a complete idiot when it comes to UNIX.
But I guess XWindows or whatever isn't in my Developer Tools. So there's no
watching a scene render. But files output beautifully.

And it works, under OX 10.4.4 on a Mactel machine.

I wonder what gcc optimizations might be employed in compiling this thing?

Best regards!

Post a reply to this message