Quick instructions how to compile POV-Ray for UNIX:

  - Download the source code from
    ftp://ftp.povray.org/pub/povray/Official/Unix/povuni_s.tgz
    to a temporary directory.

  - Uncompress the file. If you don't know how, try with these commands:
    gunzip povuni_s.tgz
    tar -xvf povuni_s.tar

  - You can now delete povuni_s.tar if you want.

  - Go to the povray31/source/ directory (cd povray31/source)

  - In this directory, go to the zlib directory (cd zlib)

  - Edit the Makefile. You may want to change the compiler to gcc (or
    any other you like), ie. change the line "CC=cc" to "CC=gcc". You may
    also want more optimizations, ie. change the line "CGLAGS=-O" to
    "CFLAGS=-O3" or higher. The default settings are just fine, thought.

  - At the command prompt type: make libz.a

  - Go to povray31/source/libpng/ (cd ../libpng/)

  - See the contents of the 'scripts' subdirectory (ls scripts) and copy
    the proper file to 'Makefile' in the current directory. For example,
    if you are using SunOS you would type: cp scripts/makefile.sun Makefile

  - Edit the Makefile and change the compiler and flags. Once again, the
    default settings are just fine and you don't have to change anything
    if you don't want to.

  - Type: make libpng.a

  - Go to povray31/source/unix (cd ../unix/)

  - Edit the makefile:

    1) If you know that you can use libpng as a shared library, you can
       leave the LIBPNG* lines as they are. Else, or if you are not sure,
       comment the line "LIBPNGLIB = -L$(PNGDIR) -lpng" (add a # at the
       beginning) and uncomment the line "LIBPNGLIB = $(PNGDIR)/libpng.a"
       (remove the # from the beginning).

    2) Do the same with the ZLIB* lines (usually you would uncomment the
       "ZLIBLIB = $(ZLIBDIR)/libz.a" line and comment the
       "ZLIBLIB = -L$(ZLIBDIR) -lz" line).

    3) If you are going to compile a xwin version, choose the proper X11
       line and comment the others. For example, if you are using a SunOS
       and the X libraries are in /usr/openwin, then uncomment the line
       "X11 = /usr/openwin" and comment the others.
       IMPORTANT NOTE: There are extra spaces at the end of some lines.
       You have to remove them or the compilation will fail.

    4) Choose the proper CFLAGS line (ie. uncomment it and comment the
       others). For example in SunOS (and most unixes) the proper CFLAGS
       line is the first one. Change the "-O2" to "-O3" if you want.

  - At the command prompt, type: gmake newxwin
    If you only want a command line version, you can type: gmake newunix
    In Linux you can type: gmake newsvga

  - If everything went fine, you should have a file named x-povray in the
    current directory. You can reduce its size by typing "strip x-povray".

  - Copy it to the directory you want it installed.

  - You can now delete the temporary directory where you downloaded the
    source.

  - Download the extra stuff from
    ftp://ftp.povray.org/pub/povray/Official/Unix/povuni_d.tgz
    and uncompress it to the same directory where you want povray installed.


-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Dear Nieminen,

 I am trying to install the POV-Ray for Unix on a Digital AlphaServer4000 5/400
System(Digital Unix 4.0).  As per your instruction, I chose makefile.dec.
It went OK upto this point.
After that, I had a problem after I typed: gmake newunix
       ksh: gmake:  not found
Since I'm a real newbie to this Unix world, I really need some help in this
regard.
 Do I have to install the gmake program somewhere on the Digital Unix /bin?
 Can I simply install in my subdirectory for the gmake to work?
 Can I get the program from the www.gnu.org site?

Thanks in advance,

Jong

Nieminen Mika wrote:

>   Quick instructions how to compile POV-Ray for UNIX:
>
>   - Download the source code from
>     ftp://ftp.povray.org/pub/povray/Official/Unix/povuni_s.tgz
>     to a temporary directory.
>
>   - Uncompress the file. If you don't know how, try with these commands:
>     gunzip povuni_s.tgz
>     tar -xvf povuni_s.tar
>
>   - You can now delete povuni_s.tar if you want.
>
>   - Go to the povray31/source/ directory (cd povray31/source)
>
>   - In this directory, go to the zlib directory (cd zlib)
>
>   - Edit the Makefile. You may want to change the compiler to gcc (or
>     any other you like), ie. change the line "CC=cc" to "CC=gcc". You may
>     also want more optimizations, ie. change the line "CGLAGS=-O" to
>     "CFLAGS=-O3" or higher. The default settings are just fine, thought.
>
>   - At the command prompt type: make libz.a
>
>   - Go to povray31/source/libpng/ (cd ../libpng/)
>
>   - See the contents of the 'scripts' subdirectory (ls scripts) and copy
>     the proper file to 'Makefile' in the current directory. For example,
>     if you are using SunOS you would type: cp scripts/makefile.sun Makefile
>
>   - Edit the Makefile and change the compiler and flags. Once again, the
>     default settings are just fine and you don't have to change anything
>     if you don't want to.
>
>   - Type: make libpng.a
>
>   - Go to povray31/source/unix (cd ../unix/)
>
>   - Edit the makefile:
>
>     1) If you know that you can use libpng as a shared library, you can
>        leave the LIBPNG* lines as they are. Else, or if you are not sure,
>        comment the line "LIBPNGLIB = -L$(PNGDIR) -lpng" (add a # at the
>        beginning) and uncomment the line "LIBPNGLIB = $(PNGDIR)/libpng.a"
>        (remove the # from the beginning).
>
>     2) Do the same with the ZLIB* lines (usually you would uncomment the
>        "ZLIBLIB = $(ZLIBDIR)/libz.a" line and comment the
>        "ZLIBLIB = -L$(ZLIBDIR) -lz" line).
>
>     3) If you are going to compile a xwin version, choose the proper X11
>        line and comment the others. For example, if you are using a SunOS
>        and the X libraries are in /usr/openwin, then uncomment the line
>        "X11 = /usr/openwin" and comment the others.
>        IMPORTANT NOTE: There are extra spaces at the end of some lines.
>        You have to remove them or the compilation will fail.
>
>     4) Choose the proper CFLAGS line (ie. uncomment it and comment the
>        others). For example in SunOS (and most unixes) the proper CFLAGS
>        line is the first one. Change the "-O2" to "-O3" if you want.
>
>   - At the command prompt, type: gmake newxwin
>     If you only want a command line version, you can type: gmake newunix
>     In Linux you can type: gmake newsvga
>
>   - If everything went fine, you should have a file named x-povray in the
>     current directory. You can reduce its size by typing "strip x-povray".
>
>   - Copy it to the directory you want it installed.
>
>   - You can now delete the temporary directory where you downloaded the
>     source.
>
>   - Download the extra stuff from
>     ftp://ftp.povray.org/pub/povray/Official/Unix/povuni_d.tgz
>     and uncompress it to the same directory where you want povray installed.
>
> --
> main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Attachments:
Download 'us-ascii' (6 KB)

I'm not really an Unix admin or anything, but I have used it for a while
(and Linux).

Usually you can install a program to a subdirectory or your user home
and then just add it to your PATH environment variable. I'd end up
adding something likt "/home/joncruz/bin:/home/joncruz/gmake/bin"

But in general it's nice if you can get the common tools installed for
everyone to use. GNU Make is pretty much the standard make (standard in
the sense that it works the same on just about any platform, and that a
lot of people count on it), so it's usually a good idea to try to get
GNU Make and GCC installed.

J Kim wrote:

> Dear Nieminen,
>
>  I am trying to install the POV-Ray for Unix on a Digital
> AlphaServer4000 5/400 System(Digital Unix 4.0).  As per your
> instruction, I chose makefile.dec.
> It went OK upto this point.
> After that, I had a problem after I typed: gmake newunix
>        ksh: gmake:  not found
> Since I'm a real newbie to this Unix world, I really need some help in
> this regard.
>  Do I have to install the gmake program somewhere on the Digital Unix
> /bin?
>  Can I simply install in my subdirectory for the gmake to work?
>  Can I get the program from the www.gnu.org site?
>
> Thanks in advance,
>
> Jong
>
> Nieminen Mika wrote:
>
>>   Quick instructions how to compile POV-Ray for UNIX:
>>
>>   - Download the source code from
>>     ftp://ftp.povray.org/pub/povray/Official/Unix/povuni_s.tgz
>>     to a temporary directory.
>>
>>   - Uncompress the file. If you don't know how, try with these
>> commands:
>>     gunzip povuni_s.tgz
>>     tar -xvf povuni_s.tar
>>
>>   - You can now delete povuni_s.tar if you want.
>>
>>   - Go to the povray31/source/ directory (cd povray31/source)
>>
>>   - In this directory, go to the zlib directory (cd zlib)
>>
>>   - Edit the Makefile. You may want to change the compiler to gcc
>> (or
>>     any other you like), ie. change the line "CC=cc" to "CC=gcc".
>> You may
>>     also want more optimizations, ie. change the line "CGLAGS=-O" to
>>
>>     "CFLAGS=-O3" or higher. The default settings are just fine,
>> thought.
>>
>>   - At the command prompt type: make libz.a
>>
>>   - Go to povray31/source/libpng/ (cd ../libpng/)
>>
>>   - See the contents of the 'scripts' subdirectory (ls scripts) and
>> copy
>>     the proper file to 'Makefile' in the current directory. For
>> example,
>>     if you are using SunOS you would type: cp scripts/makefile.sun
>> Makefile
>>
>>   - Edit the Makefile and change the compiler and flags. Once again,
>> the
>>     default settings are just fine and you don't have to change
>> anything
>>     if you don't want to.
>>
>>   - Type: make libpng.a
>>
>>   - Go to povray31/source/unix (cd ../unix/)
>>
>>   - Edit the makefile:
>>
>>     1) If you know that you can use libpng as a shared library, you
>> can
>>        leave the LIBPNG* lines as they are. Else, or if you are not
>> sure,
>>        comment the line "LIBPNGLIB = -L$(PNGDIR) -lpng" (add a # at
>> the
>>        beginning) and uncomment the line "LIBPNGLIB =
>> $(PNGDIR)/libpng.a"
>>        (remove the # from the beginning).
>>
>>     2) Do the same with the ZLIB* lines (usually you would uncomment
>> the
>>        "ZLIBLIB = $(ZLIBDIR)/libz.a" line and comment the
>>        "ZLIBLIB = -L$(ZLIBDIR) -lz" line).
>>
>>     3) If you are going to compile a xwin version, choose the proper
>> X11
>>        line and comment the others. For example, if you are using a
>> SunOS
>>        and the X libraries are in /usr/openwin, then uncomment the
>> line
>>        "X11 = /usr/openwin" and comment the others.
>>        IMPORTANT NOTE: There are extra spaces at the end of some
>> lines.
>>        You have to remove them or the compilation will fail.
>>
>>     4) Choose the proper CFLAGS line (ie. uncomment it and comment
>> the
>>        others). For example in SunOS (and most unixes) the proper
>> CFLAGS
>>        line is the first one. Change the "-O2" to "-O3" if you want.
>>
>>   - At the command prompt, type: gmake newxwin
>>     If you only want a command line version, you can type: gmake
>> newunix
>>     In Linux you can type: gmake newsvga
>>
>>   - If everything went fine, you should have a file named x-povray
>> in the
>>     current directory. You can reduce its size by typing "strip
>> x-povray".
>>
>>   - Copy it to the directory you want it installed.
>>
>>   - You can now delete the temporary directory where you downloaded
>> the
>>     source.
>>
>>   - Download the extra stuff from
>>     ftp://ftp.povray.org/pub/povray/Official/Unix/povuni_d.tgz
>>     and uncompress it to the same directory where you want povray
>> installed.
>>
>> --
>> ma
>> n(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
>>
>> ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*-
>> Warp -*/
>
--
"My new computer's got the clocks, it rocks
But it was obsolete before I opened the box" - W.A.Y.

Post a reply to this message

J Kim wrote:

>  I am trying to install the POV-Ray for Unix on a Digital
> AlphaServer4000 5/400 System(Digital Unix 4.0).  As per your
> instruction, I chose makefile.dec.
> It went OK upto this point.
> After that, I had a problem after I typed: gmake newunix
>        ksh: gmake:  not found
> Since I'm a real newbie to this Unix world, I really need some help in
> this regard.
>  Do I have to install the gmake program somewhere on the Digital Unix
> /bin?
>  Can I simply install in my subdirectory for the gmake to work?
>  Can I get the program from the www.gnu.org site?
(snip)
> >   - At the command prompt, type: gmake newxwin
> >     If you only want a command line version, you can type: gmake
> > newunix
> >     In Linux you can type: gmake newsvga
> >

You ought to be able to get by using make rather than gmake.  It was
never my intent to require gmake (though it has at times hidden a few
bugs in the makefile that other versions of make didn't tolerate so
well, but I think those are fixed now).  Let me know if that doesn't
work.

-Mark Gordon

Post a reply to this message

Dear Mark,
 I have tried using the 'make' instead of 'gmake', since it would to take
quite some time for me
to get the 'gmake' program(or part of the programs) and install.
After issuing 'make newunix' under the directory .... /source/unix,
I got following messages:
(I have not changed cc to gcc yet.)

Thanks in advance,
Jong
-------------------------------------------------
/temp/povray31/source/unix >make newunix
cc -O2 -ansi -c -DCOMPILER_VER=\".`uname`.cc\" -I. -I.. -I../libpng
-I../zlib -I
/usr/bin/X11  /include ../polysolv.c
cc: Warning: ../polysolv.c, line 66: # not in column 1 is ignored, skipping
to e
nd of line.
 #define FUDGE_FACTOR1 1.0e12
-^
cc: Warning: ../polysolv.c, line 69: # not in column 1 is ignored, skipping
to e
nd of line.
 #define FUDGE_FACTOR2 -1.0e-5
-^
cc: Warning: ../polysolv.c, line 72: # not in column 1 is ignored, skipping
to e
nd of line.
 #define FUDGE_FACTOR3 1.0e-7
-^
cc: Error: ../polysolv.c, line 1085: In this statement, "FUDGE_FACTOR1" is
not d
eclared.
      if (fabs(biggest / x[i]) > FUDGE_FACTOR1)
---------------------------------^
*** Exit 1
Stop.
*** Exit 1 (ignored)

====================================
Mark Gordon wrote:

> J Kim wrote:
>
> >  I am trying to install the POV-Ray for Unix on a Digital
> > AlphaServer4000 5/400 System(Digital Unix 4.0).  As per your
> > instruction, I chose makefile.dec.
> > It went OK upto this point.
> > After that, I had a problem after I typed: gmake newunix
> >        ksh: gmake:  not found
> > Since I'm a real newbie to this Unix world, I really need some help in
> > this regard.
> >  Do I have to install the gmake program somewhere on the Digital Unix
> > /bin?
> >  Can I simply install in my subdirectory for the gmake to work?
> >  Can I get the program from the www.gnu.org site?
> (snip)
> > >   - At the command prompt, type: gmake newxwin
> > >     If you only want a command line version, you can type: gmake
> > > newunix
> > >     In Linux you can type: gmake newsvga
> > >
>
> You ought to be able to get by using make rather than gmake.  It was
> never my intent to require gmake (though it has at times hidden a few
> bugs in the makefile that other versions of make didn't tolerate so
> well, but I think those are fixed now).  Let me know if that doesn't
> work.
>
> -Mark Gordon

Post a reply to this message

"J. Kim" wrote:
> 
> Dear Mark,
>  I have tried using the 'make' instead of 'gmake', since it would to take
> quite some time for me
> to get the 'gmake' program(or part of the programs) and install.
> After issuing 'make newunix' under the directory .... /source/unix,
> I got following messages:
> (I have not changed cc to gcc yet.)
> 
> Thanks in advance,
> Jong
> -------------------------------------------------
> /temp/povray31/source/unix >make newunix
> cc -O2 -ansi -c -DCOMPILER_VER=\".`uname`.cc\" -I. -I.. -I../libpng
> -I../zlib -I
> /usr/bin/X11  /include ../polysolv.c
> cc: Warning: ../polysolv.c, line 66: # not in column 1 is ignored, skipping
> to e
> nd of line.
>  #define FUDGE_FACTOR1 1.0e12
> -^
> cc: Warning: ../polysolv.c, line 69: # not in column 1 is ignored, skipping
> to e
> nd of line.
>  #define FUDGE_FACTOR2 -1.0e-5
> -^
> cc: Warning: ../polysolv.c, line 72: # not in column 1 is ignored, skipping
> to e
> nd of line.
>  #define FUDGE_FACTOR3 1.0e-7
> -^
> cc: Error: ../polysolv.c, line 1085: In this statement, "FUDGE_FACTOR1" is
> not d
> eclared.
>       if (fabs(biggest / x[i]) > FUDGE_FACTOR1)
> ---------------------------------^
> *** Exit 1
> Stop.
> *** Exit 1 (ignored)

Those errors are coming from cc, not make.  It looks like your C
compiler (or preprocessor) doesn't like the fact that some of the
#define's in this file don't start immediately at the beginning of the
line.  It looks like the author of this piece of code decided to make
the code a little more human-friendly by indenting his cpp directives,
but your compiler doesn't like it.  Just go in and erase the space from
the beginning of lines 66, 69, and 72, and let me know if it compiles
without complaining.

Of course, changing cc to gcc would probably fix that too. ;-)  I'd
still like to know whether that fixes the problem, since I'd prefer the
code be more portable.

-Mark Gordon

Post a reply to this message

Dear Mark,
 Guess what!
I've removed the leading spaces of the 66, 69, and 72nd lines. Then issued
' make newunix'.
I did not have any error messages. And I've got the following files generated.

  /user3/prof/jjkim/temp/povray31/source/unix >ls -tla pov*
-rwxr-xr-x   1 jjkim    prof     1064960  1-17 17:34 povray
-rw-r--r--   1 jjkim    prof       46760    1-17 17:34 povray.o
-rw-r--r--   1 jjkim    prof       20126  11-22 10:08 povray.1   (and povrayrc
also)

Following lines are shown upon the screen, when I issued 'make newunix'.
Am I close to the final? Do I simply issue 'povray' for running the program?

Thank you so much,

Jong
-----------------------------------------
cc -O2 -ansi -c -DCOMPILER_VER=\".`uname`.cc\" -I. -I.. -I../libpng -I../zlib -I
/usr/bin/X11  /include ../povray.c
cc -O2 -ansi -c -DCOMPILER_VER=\".`uname`.cc\" -I. -I.. -I../libpng -I../zlib -I
/usr/bin/X11  /include ../render.c
cc -O2 -ansi -c -DCOMPILER_VER=\".`uname`.cc\" -I. -I.. -I../libpng -I../zlib -I
/usr/bin/X11  /include ../userio.c
cc -O2 -ansi -c -DCOMPILER_VER=\".`uname`.cc\" -I. -I.. -I../libpng -I../zlib -I
/usr/bin/X11  /include ../vbuffer.c
cc ./atmosph.o   ./bbox.o      ./bcyl.o      ./bezier.o    ./blob.o      ./boxes
.o     ./bsphere.o   ./camera.o    ./chi2.o      ./colour.o    ./cones.o     ./c
<deleted a few lines>
--------------------------
Mark Gordon wrote:

> "J. Kim" wrote:
> >
> > Dear Mark,
> >  I have tried using the 'make' instead of 'gmake', since it would to take
> > quite some time for me
> > to get the 'gmake' program(or part of the programs) and install.
> > After issuing 'make newunix' under the directory .... /source/unix,
> > I got following messages:
> > (I have not changed cc to gcc yet.)
> >
> > Thanks in advance,
> > Jong
> > -------------------------------------------------
> > /temp/povray31/source/unix >make newunix
> > cc -O2 -ansi -c -DCOMPILER_VER=\".`uname`.cc\" -I. -I.. -I../libpng
> > -I../zlib -I
> > /usr/bin/X11  /include ../polysolv.c
> > cc: Warning: ../polysolv.c, line 66: # not in column 1 is ignored, skipping
> > to e
> > nd of line.
> >  #define FUDGE_FACTOR1 1.0e12
> > -^
> > cc: Warning: ../polysolv.c, line 69: # not in column 1 is ignored, skipping
> > to e
> > nd of line.
> >  #define FUDGE_FACTOR2 -1.0e-5
> > -^
> > cc: Warning: ../polysolv.c, line 72: # not in column 1 is ignored, skipping
> > to e
> > nd of line.
> >  #define FUDGE_FACTOR3 1.0e-7
> > -^
> > cc: Error: ../polysolv.c, line 1085: In this statement, "FUDGE_FACTOR1" is
> > not d
> > eclared.
> >       if (fabs(biggest / x[i]) > FUDGE_FACTOR1)
> > ---------------------------------^
> > *** Exit 1
> > Stop.
> > *** Exit 1 (ignored)
>
> Those errors are coming from cc, not make.  It looks like your C
> compiler (or preprocessor) doesn't like the fact that some of the
> #define's in this file don't start immediately at the beginning of the
> line.  It looks like the author of this piece of code decided to make
> the code a little more human-friendly by indenting his cpp directives,
> but your compiler doesn't like it.  Just go in and erase the space from
> the beginning of lines 66, 69, and 72, and let me know if it compiles
> without complaining.
>
> Of course, changing cc to gcc would probably fix that too. ;-)  I'd
> still like to know whether that fixes the problem, since I'd prefer the
> code be more portable.
>
> -Mark Gordon

Post a reply to this message

"J. Kim" <jjk### [at] mmewhaackr> writes:

> Dear Mark,
>  Guess what!
> I've removed the leading spaces of the 66, 69, and 72nd lines. Then issued
> ' make newunix'.
> I did not have any error messages. And I've got the following files generated
> 
>   /user3/prof/jjkim/temp/povray31/source/unix >ls -tla pov*
> -rwxr-xr-x   1 jjkim    prof     1064960  1-17 17:34 povray
> -rw-r--r--   1 jjkim    prof       46760    1-17 17:34 povray.o
> -rw-r--r--   1 jjkim    prof       20126  11-22 10:08 povray.1 
> 
> Following lines are shown upon the screen, when I issued 'make newunix'.
> Am I close to the final? Do I simply issue 'povray' for running the program?

Yes. The executable povray should work now. The makefile can in fact create
three different versions of povray: plain ascii interface, X, and SVGA.
By selecting "newunix" you tell make that you want to create a new, 
different version. If you simply type "make" instead, it shouldn't compile
anything anymore.

As I said in the beginning, "povray" should work now. In my opinion, it
is a good thing to create the X version, too. Simply try "make newxwin".
Perhaps you may have o adjust the location of the X include files and
libraries in the makefile. By calling "x-povray" with the option "-d" 
you should see the image while it's rendered (under the assumption that 
you have an X server running). Furthermore, you can get an "mosaic preview"
with the option "+sp4".

Thomas 

--
http://thomas.willhalm.de/ (includes pgp key)

Post a reply to this message

Thomas Willhalm <tho### [at] willhalmde> wrote:
: By calling "x-povray" with the option "-d" 
: you should see the image while it's rendered

  You mean "+d"?

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message

Nieminen Juha <war### [at] punarastascstutfi> writes:

> Thomas Willhalm <tho### [at] willhalmde> wrote:
> : By calling "x-povray" with the option "-d" 
> : you should see the image while it's rendered
> 
>   You mean "+d"?

Yes, I do. (I'm sorry, when I've confused others.)

Thomas

-- 
http://thomas.willhalm.de/ (includes pgp key)

Post a reply to this message