I'm encountering some similar problems discussed here while trying to
compile the latest PovRay. I found a solution to the problem trying to
compile the docs in this newsgroup, but I don't see it as a real solution
(remove docs from the SUBDIRS line of the Makefile) and it's a bug that
needs to be fixed.

I also saw a "fix" for the tiff problem, which I haven't encountered as of
yet as I haven't gotten that far, but I've made note of it for future
reference.

I haven't found anything regarding the problem I now face. I get this error
in compiling for solaris 8 x86, gcc 3.1.1, gnu make 3.7.9:

Making all in src
make[1]: Entering directory `/sw/pgmstore/admpubsw/povray/povray-3.50c/src'
c++ -DPREFIX=\"/package/povray-3.5\"
-DPOV_LIB_DIR=\"/package/povray-3.5/share/p
ovray-3.5\" -DCOMPILER_VER=\".Linux.gcc\"
-DSYSCONFDIR=\"/etc/localhost/povray-3
..5\" -DUSE_IO_RESTRICTIONS=\"\"   -I/public/include -L/public/lib  `if [
"Xgcc"
= "Xgcc" ]; then echo "-Wno-multichar"; fi ` -O3 -finline-functions
-ffast-math
-fomit-frame-pointer -funroll-loops -fexpensive-optimizations -malign-double
-fo
ptimize-sibling-calls -minline-all-stringops -Wno-multichar -c atmosph.cpp
c++ -DPREFIX=\"/package/povray-3.5\"
-DPOV_LIB_DIR=\"/package/povray-3.5/share/p
ovray-3.5\" -DCOMPILER_VER=\".Linux.gcc\"
-DSYSCONFDIR=\"/etc/localhost/povray-3
..5\" -DUSE_IO_RESTRICTIONS=\"\"   -I/public/include -L/public/lib  `if [
"Xgcc"
= "Xgcc" ]; then echo "-Wno-multichar"; fi ` -O3 -finline-functions
-ffast-math
-fomit-frame-pointer -funroll-loops -fexpensive-optimizations -malign-double
-fo
ptimize-sibling-calls -minline-all-stringops -Wno-multichar -c bbox.cpp
In file included from bbox.cpp:47:
optout.h:49:2: #error You must complete the following DISTRIBUTION_MESSAGE
macro
bbox.cpp: In function `int sort_and_split(BBOX_TREE**, BBOX_TREE**&, long
int*,
   long int, long int)':
bbox.cpp:1872: warning: assignment to `long int' from `double'
bbox.cpp:1872: warning: argument to `long int' from `double'
make[1]: *** [bbox.o] Error 1
make[1]: Leaving directory `/sw/pgmstore/admpubsw/povray/povray-3.50c/src'
make: *** [all-recursive] Error 1


Any help is greatly and urgently appreciated.

--
Carl B. Constantine
cco### [at] cscuvicca

Post a reply to this message

In article <web.3e833bc6b517b6f4a7261b750@news.povray.org> , "cconstan" 
<cco### [at] cscuvicca> wrote:

> In file included from bbox.cpp:47:
> optout.h:49:2: #error You must complete the following DISTRIBUTION_MESSAGE
> macro
> bbox.cpp: In function `int sort_and_split(BBOX_TREE**, BBOX_TREE**&, long
> int*,
>    long int, long int)':
> bbox.cpp:1872: warning: assignment to `long int' from `double'
> bbox.cpp:1872: warning: argument to `long int' from `double'
> make[1]: *** [bbox.o] Error 1
> make[1]: Leaving directory `/sw/pgmstore/admpubsw/povray/povray-3.50c/src'
> make: *** [all-recursive] Error 1
>
>
> Any help is greatly and urgently appreciated.

*Read* the error message -- it really helps!!!

    Thorsten

____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thorsten Froehlich wrote:
>> Any help is greatly and urgently appreciated.
>
>*Read* the error message -- it really helps!!!

I *did* but it does not help. There is nothing in any docs that I've seen
about the DISTRIBUTION_MESSAGE macro, where it is or what should be done
with it. all I've done is ./configure, make so far, just like the docs say.
No where does it say I have to touch any macro. That should probably be set
in the Configure script anyway, which means this is bug (IMHO).

--
Carl B. Constantine

Post a reply to this message

> I *did* but it does not help. There is nothing in any docs that I've seen
> about the DISTRIBUTION_MESSAGE macro, where it is or what should be done
> with it.

	In the source distribution of POV-Ray, that I assume you got since
you're trying to compile it, there is a file called README. The problem you
face is not a problem and is actually well described in this README file.
Not to be confused with the README.unix file that you should read as well.
	README and INSTALL files are usually considered as useful docs.

> all I've done is ./configure, make so far, just like the docs say.
> No where does it say I have to touch any macro. That should probably be set
> in the Configure script anyway, which means this is bug (IMHO).

	If you look a few threads ago, you'll find one called 'New configure
script' which in principle answers this particular point. Not tested on
Solaris though.

Post a reply to this message

cconstan wrote:
> 
> I *did* but it does not help. There is nothing in any docs that I've seen
> about the DISTRIBUTION_MESSAGE macro, where it is or what should be done
> with it. all I've done is ./configure, make so far, just like the docs say.
> No where does it say I have to touch any macro. 

What's not understandable about:

optout.h:49:2: #error You must complete the following DISTRIBUTION_MESSAGE
macro

???

optout.h, line 49 says:

#define DISTRIBUTION_MESSAGE_1 "This is an unofficial version compiled
by:"
#error You must complete the following DISTRIBUTION_MESSAGE macro
#define DISTRIBUTION_MESSAGE_2 " FILL IN NAME
HERE........................."

Apart from that as Nicolas mentions the package contains a README file
that describes exactly this.   

> That should probably be set
> in the Configure script anyway, which means this is bug (IMHO).

This is not a bug but an intended feature!

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 28 Feb. 2003 _____./\/^>_*_<^\/\.______

Post a reply to this message

In article <web.3e8355f0a517a360a7261b750@news.povray.org> , "cconstan" 
<cco### [at] cscuvicca> wrote:

>>*Read* the error message -- it really helps!!!
>
> I *did* but it does not help. There is nothing in any docs that I've seen
> about the DISTRIBUTION_MESSAGE macro, where it is or what should be done
> with it. all I've done is ./configure, make so far, just like the docs say.

The POV-Ray source code precisely tells you what to do in the message that
is displayed.  There is an #error directive in that file and it gives you
instructions what to do:

"You must complete the following DISTRIBUTION_MESSAGE macro"

So you open that file and complete the macro that clearly says "FILL IN NAME
HERE" and which follows the error directive line exactly as stated in the
instructions.  Naturally you then remove the error directive line.

> No where does it say I have to touch any macro. That should probably be set
> in the Configure script anyway, which means this is bug (IMHO).

The only "bug" here is that you read neither the documentation (the README
file) nor the #error directive message.  As a matter of fact the directive
is there for exactly this reason because in the past countless people did
not read any documentation and started to distribute unofficial versions of
POV-Ray that violated the POV-Ray license.

So if you consider it a bug that the configure script does not force you to
read the documentation, I think your expectations are unrealistic...

    Thorsten

____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Nicolas Calimet wrote:
>> I *did* but it does not help. There is nothing in any docs that I've seen
>> about the DISTRIBUTION_MESSAGE macro, where it is or what should be done
>> with it.
>
> In the source distribution of POV-Ray, that I assume you got since
>you're trying to compile it, there is a file called README. The problem you
>face is not a problem and is actually well described in this README file.
>Not to be confused with the README.unix file that you should read as well.
> README and INSTALL files are usually considered as useful docs.

Ok ok, so I read README.unix and INSTALL but not README. Defined and now
compiling just fine so far. Haven't hit the TIFF problem yet.

Thanks for the help. Sorry for the trouble, my bad DOH!

--
Carl B. Constantine

Post a reply to this message

Thorsten Froehlich wrote:
>> No where does it say I have to touch any macro. That should probably be set
>> in the Configure script anyway, which means this is bug (IMHO).
>
>The only "bug" here is that you read neither the documentation (the README
>file) nor the #error directive message.  As a matter of fact the directive
>is there for exactly this reason because in the past countless people did
>not read any documentation and started to distribute unofficial versions of
>POV-Ray that violated the POV-Ray license.

ok, so it's not a bug. I read the README.unix but not README as they
traditionally contain very unusful information for Unix people.

>So if you consider it a bug that the configure script does not force you to
>read the documentation, I think your expectations are unrealistic...

No, I consider it someone frivolous (sp?) to require the person doing the
compile to put there name in a macro for crying out loud. I shouldn't have
to do it at all.

Post a reply to this message

cconstan wrote:
> ok, so it's not a bug. I read the README.unix but not README as they
> traditionally contain very unusful information for Unix people.

'traditionally'? Almost every application under at least *BSD and 
GNU/Linux has README's which most often contain _essential_ information.

> No, I consider it someone frivolous (sp?) to require the person doing the
> compile to put there name in a macro for crying out loud. I shouldn't have
> to do it at all.

It is a support issue, I suppose. Forcing you to do that relieves the 
POV team from having to support unofficial compiles, which are 
impossible for the POV team to test and provide quality assurance.

Not to mention the priviledge you get of putting your name in the 
executable ;-)

Post a reply to this message

In article <web.3e837ac3a517a360a7261b750@news.povray.org> , "cconstan" 
<cco### [at] cscuvicca> wrote:

>>So if you consider it a bug that the configure script does not force you to
>>read the documentation, I think your expectations are unrealistic...
>
> No, I consider it someone frivolous (sp?) to require the person doing the
> compile to put there name in a macro for crying out loud. I shouldn't have
> to do it at all.

I told you why:

"As a matter of fact the directive
is there for exactly this reason because in the past countless people did
not read any documentation and started to distribute unofficial versions of
POV-Ray that violated the POV-Ray license."

The license requires that you provide the information your are supposed to
enter there if you want to distribute the version you compiled.

    Thorsten

____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg

I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message