Dawn McKnight wrote:

> No; fortunately, binaries compiled for one Windows machine will work on
> another. 8)  Which means that smart people can do the compiling, while
> dummies like me can just use it. 8)

That's exactly the same with solaris. Of course linux and solaris are two 
different OS. Also if you have different CPU architecture it is obvious 
that you need to recompile.

-- 
http://objects.povworld.org - the POV-Ray Objects Collection

Post a reply to this message

On Thu, 01 Aug 2002 19:27:01 -0400, Micha Riser wrote:

> Mark Gordon wrote:
> 
>> ~/.povray.conf or /usr/local/etc/povray.conf (if built with
>> --prefix=/usr, then /etc/povray.conf).
>> 
> And what in it to allow everything?
 
[File I/O Security]
none

[Shellout Security]
allowed

-Mark Gordon

Post a reply to this message

Dawn McKnight <blu### [at] maccom> wrote:
> This is kind of why *nix isn't going to be replacing Winders as a 
> populist OS anytime soon.  Argh.

  I doubt that *compiling* things in Windows is any easer than in Unix.
  At least in Unix you almost always have a C/C++ compiler. In Windows
you usually don't have any.
  Also compiling C/C++ in Unix is almost always done in the same way.
In windows there are plenty of compilers, all of them used differently.
There's no general agreement on how windows source should be distributed
while in Unix you almost always get configure/makefile scripts, which should
work in almost any Unix flavour, regardless of the platform.

  Distributing a program in source code format is useful in Unix, because
it can be compiled so easily. Distributing a windows program in source code
form is mostly useless because almost no-one can compile it. I wouldn't say
that the windows situation is better.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

>Try to add '-ljpeg -ltiff' to the LIBS in Makefile. For X11 I do not know 
>what there is missing. But you can add '#define X_DISPLAY_MISSING' to 
>conf.h which will give you a build without X11.
>
I did that; I also tried (in a seperate pass) uncommenting the line in 
conf.h which says to uncomment it if you're not using X11.  Neither 
resulted in a successful compilation.

Perhaps, in the next revision of the source code released, there should 
be a 'unix' option to make, like there was under 3.1, where a text-only 
version is created?

Post a reply to this message

In article <3D4### [at] maccom>,
 Dawn McKnight <blu### [at] maccom> wrote:

> I did that; I also tried (in a seperate pass) uncommenting the line in 
> conf.h which says to uncomment it if you're not using X11.  Neither 
> resulted in a successful compilation.

Uncomment and change from "#undef" to "#define".

-- 
Christopher James Huff <chr### [at] maccom>
POV-Ray TAG e-mail: chr### [at] tagpovrayorg
TAG web site: http://tag.povray.org/

Post a reply to this message

>
>
>Uncomment and change from "#undef" to "#define".
>
Okay; I did that.  Now I'm getting complaints that it can't find library 
-ljpeg.

I've downloaded and installed the jpeg library in /usr/local/lib; in 
/usr/lib; in /usr/openwin/lib, all of which seem to be indicated at 
various places in the makefile.

It still can't find the library.

This is really quite frustrating.  Am I really that stupid?

Post a reply to this message

In article <3D4### [at] maccom>, Dawn McKnight <blu### [at] maccom> 
wrote:

> >
> >
> >Uncomment and change from "#undef" to "#define".
> >
> Okay; I did that.  Now I'm getting complaints that it can't find library 
> -ljpeg.
> 
> I've downloaded and installed the jpeg library in /usr/local/lib; in 
> /usr/lib; in /usr/openwin/lib, all of which seem to be indicated at 
> various places in the makefile.
> 
> It still can't find the library.
> 
> This is really quite frustrating.  Am I really that stupid?

Specify the directory with -L? Try "-L /usr/lib/". Or maybe use "-l 
libjpeg". Can't really help more, I'm not using the makefile on my 
system, I made a ProjectBuilder project.

-- 
Christopher James Huff <chr### [at] maccom>
POV-Ray TAG e-mail: chr### [at] tagpovrayorg
TAG web site: http://tag.povray.org/

Post a reply to this message

Thanks, anyway, Christopher.

I just don't understand how, when I run the configure script, it can 
apparently find my jpeg libraries (as evidenced by the line: checking 
for jpeg_std_error in -ljpeg... yes ) but then the make for src can't.

I'm not going to be generating any more spam over this issue, though... 
not because I've succeeded and gone away, but because I'm giving up and 
going away.

Post a reply to this message

"Mark Gordon" <mtg### [at] povrayorg> wrote in message
news:pan### [at] povrayorg...
> On Thu, 01 Aug 2002 19:27:01 -0400, Micha Riser wrote
>>
> > And what in it to allow everything?
>
> [File I/O Security]
> none
>
> [Shellout Security]
> allowed
>

Just a suggestion, but someone might want to put that into the README.
Or change the error message to be more intuitive.  That drove me nuts!!!!!
I thought it was saying the Unix file permissions were preventing read
access.  I thought the code was broken because trussing the process
showed me that it opened the .pov file and got a valid file descriptor
for it.

-Dave

Post a reply to this message

Mark Gordon <mtg### [at] povrayorg> wrote:
> ~/.povray.conf or /usr/local/etc/povray.conf (if built with --prefix=/usr,
> then /etc/povray.conf).

  I suppose these files can't be opened with pov-script, no matter which
permissions are set (in the same way as winpov works with its own settings
files)?

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message