 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I receive the following error when issuing 'make' on a RH9 machine (the
build works fine on a FC2 machine, however):
<snip>
g++ -DHAVE_CONFIG_H -DPOVLIBDIR="/home/fenn/sware/share/povray-3.6"
-DPOVCONFDIR="/home/fenn/sware/etc/povray/3.6"
-DPOVCONFDIR_BACKWARD="/home/fenn/sware/etc" -I. -I. -I.. -I.. -I../source
-I../source/base -I../source/frontend -I../source -I../libraries/zlib
-I../libraries/png -I../libraries/tiff/libtiff -I../libraries/tiff/libtiff
-I/usr/X11R6/include -pipe -Wno-multichar -O3 -msse -mfpmath=sse
-march=pentium3 -mcpu=pentium3 -malign-double -minline-all-stringops
-c -o unix.o `test -f 'unix.cpp' || echo './'`unix.cpp
In file included from ../source/frontend/configfrontend.h:37,
from ../source/frontend/defaultrenderfrontend.h:36,
from unix.cpp:81:
.../libraries/zlib/config.h:98:1: warning: "PACKAGE" redefined
In file included from unix.cpp:76:
.../conf.h:98:1: warning: this is the location of the previous definition
In file included from ../source/frontend/configfrontend.h:37,
from ../source/frontend/defaultrenderfrontend.h:36,
from unix.cpp:81:
.../libraries/zlib/config.h:101:1: warning: "PACKAGE_BUGREPORT" redefined
In file included from unix.cpp:76:
.../conf.h:101:1: warning: this is the location of the previous definition
In file included from ../source/frontend/configfrontend.h:37,
from ../source/frontend/defaultrenderfrontend.h:36,
from unix.cpp:81:
.../libraries/zlib/config.h:104:1: warning: "PACKAGE_NAME" redefined
In file included from unix.cpp:76:
.../conf.h:104:1: warning: this is the location of the previous definition
In file included from ../source/frontend/configfrontend.h:37,
from ../source/frontend/defaultrenderfrontend.h:36,
from unix.cpp:81:
.../libraries/zlib/config.h:107:1: warning: "PACKAGE_STRING" redefined
In file included from unix.cpp:76:
.../conf.h:107:1: warning: this is the location of the previous definition
In file included from ../source/frontend/configfrontend.h:37,
from ../source/frontend/defaultrenderfrontend.h:36,
from unix.cpp:81:
.../libraries/zlib/config.h:110:1: warning: "PACKAGE_TARNAME" redefined
In file included from unix.cpp:76:
.../conf.h:110:1: warning: this is the location of the previous definition
In file included from ../source/frontend/configfrontend.h:37,
from ../source/frontend/defaultrenderfrontend.h:36,
from unix.cpp:81:
.../libraries/zlib/config.h:113:1: warning: "PACKAGE_VERSION" redefined
In file included from unix.cpp:76:
.../conf.h:113:1: warning: this is the location of the previous definition
In file included from ../source/frontend/configfrontend.h:37,
from ../source/frontend/defaultrenderfrontend.h:36,
from unix.cpp:81:
.../libraries/zlib/config.h:125:1: warning: "VERSION" redefined
In file included from unix.cpp:76:
.../conf.h:146:1: warning: this is the location of the previous definition
In file included from ../source/povray.h:38,
from ../source/optout.h:39,
from unix.cpp:85:
.../source/frame.h:84: syntax error before `*' token
.../source/frame.h:1319: syntax error before `*' token
.../source/frame.h:1324: syntax error before `*' token
.../source/frame.h:1330: syntax error before `*' token
(many more errors omitted)
make: *** [all] Error 2
</snip>
I have the full config.log and log from the build, if it will help.
Regards,
Tim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.40fdaab3299dc4434e6ed3100@news.povray.org> , "Tim F"
<fen### [at] stanford edu> wrote:
> I receive the following error when issuing 'make' on a RH9 machine (the
> build works fine on a FC2 machine, however):
This certainly belongs to povray.unix ...
Either way, from the messages (the warnings in particular) it seems for some
odd reason the from config.h (the cone from zlib rather than POV-Ray's) gets
included all over the place. I don't know why this would happen on one
system but not another.
If you want to work around it quickly I would suggest you rename the
config.h in its directory and then build everything again. Correct the name
of the config.h in the zlib files that will certainly report an eror and you
should be all set.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.40fdaab3299dc4434e6ed3100@news.povray.org> , "Tim F"
<fen### [at] stanfordedu> wrote:
> I receive the following error when issuing 'make' on a RH9 machine (the
> build works fine on a FC2 machine, however):
This certainly belongs to povray.unix ...
Either way, from the messages (the warnings in particular) it seems for some
odd reason the from config.h (the cone from zlib rather than POV-Ray's) gets
included all over the place. I don't know why this would happen on one
system but not another.
If you want to work around it quickly I would suggest you rename the
config.h in its directory and then build everything again. Correct the name
of the config.h in the zlib files that will certainly report an eror and you
should be all set.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi Tim :-)
> I have the full config.log and log from the build, if it will help.
Please send me all config.log's (including those in the libraries)
in a .tar.bz2 archive at the e-mail address given in the INSTALL file.
As you suggest, include also the full make log.
Can you additionally post here the console output of configure
(_not_ the config.log file) when ran on your fedora core 2 distro ?
fup-to p.unix
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote:
> In article <web.40fdaab3299dc4434e6ed3100@news.povray.org> , "Tim F"
> <fen### [at] stanfordedu> wrote:
>
> > I receive the following error when issuing 'make' on a RH9 machine (the
> > build works fine on a FC2 machine, however):
>
> This certainly belongs to povray.unix ...
>
<sigh> I thought that, but as explicity described in the bug-reporting FAQ:
http://news.povray.org/povray.announce.frequently-asked-questions/thread/%3Cfpupiu02i1198jbb38i3o06hv6is1a3uar%404ax.co
m%3E/
<quote>
We insist that you first post a description of the problem in
povray.general, so that others may investigate it on their own
systems. This will aid in discovering whether it is
platform-dependent, and hopefully will also uncover some work-arounds
and a possible bugfix in the subsequent discussion from those who are
familiar with the POV-Ray source code.
</quote>
>
> Either way, from the messages (the warnings in particular) it seems for some
> odd reason the from config.h (the cone from zlib rather than POV-Ray's) gets
> included all over the place. I don't know why this would happen on one
> system but not another.
>
From looking around a bit, the zlib libraries did *NOT* need be built on my
FC2 machine, but were required in the RH9 machine - therefore, the
.../libraries/zlib path was included during the build, which was causing the
problem.
This raises another question - why not leave the image library dependencies
external, and just not include them with the release?
> If you want to work around it quickly I would suggest you rename the
> config.h in its directory and then build everything again. Correct the name
> of the config.h in the zlib files that will certainly report an eror and you
> should be all set.
>
I renamed config.h in the /unix directory, changed all the #includes, and
the build worked. However, I wouldn't consider it a proper solution.
Regards,
Tim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.40fea468a404e2e2300017f40@news.povray.org> , "Tim F"
<fen### [at] stanfordedu> wrote:
> We insist that you first post a description of the problem in
> povray.general, so that others may investigate it on their own
> systems. This will aid in discovering whether it is
> platform-dependent, and hopefully will also uncover some work-arounds
> and a possible bugfix in the subsequent discussion from those who are
> familiar with the POV-Ray source code.
That this is for *binary* versions of POV-Ray should be absolutely obvious
to everyone!
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <web.40fea468a404e2e2300017f40@news.povray.org> , "Tim F"
<fen### [at] stanfordedu> wrote:
> This raises another question - why not leave the image library dependencies
> external, and just not include them with the release?
Because many people have extremely outdated versions and the start reporting
problems in POV-Ray resulting from them having linked POV-Ray with outdated
obsolete buggy libraries that had been fixed a long time ago. We only
promise POV-Ray to run with the supplied image library versions (or newer if
you compile POV-Ray yourself). Anything older will likely not work. Hence
we supply everything needed to build a known to work version of POV-Ray
source code on every platform.
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote:
> In article <web.40fea468a404e2e2300017f40@news.povray.org> , "Tim F" wrote:
>
> > We insist that you first post a description of the problem in
> > povray.general, so that others may investigate it on their own
> > systems. This will aid in discovering whether it is
> > platform-dependent, and hopefully will also uncover some work-arounds
> > and a possible bugfix in the subsequent discussion from those who are
> > familiar with the POV-Ray source code.
>
> That this is for *binary* versions of POV-Ray should be absolutely obvious
> to everyone!
>
? It is? I don't know the problem I'm seeing is only relevant to the *nix
version of the source (since I have no other platforms to test on), and my
impression was that this was the reasoning for the wording of the FAQ.
The point is, I'm just a dumb end user - I am in no position to say the
bugreporting FAQ is invalid in this case, since no wording is present to
suggest it only applies in the case of binary or source releases. If this
isn't true, fix the FAQ.
Warning: IANAL.
Regards,
-Tim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tim F wrote:
>>
>>That this is for *binary* versions of POV-Ray should be absolutely obvious
>>to everyone!
>>
>
> ? It is? I don't know the problem I'm seeing is only relevant to the *nix
> version of the source (since I have no other platforms to test on), and my
> impression was that this was the reasoning for the wording of the FAQ.
If you don't know the reason for the compile error you get it is quite
unreasonable to assume this could be a bug in POV-Ray. If such an error
was caused by a problem in the POV-Ray source how do you imagine that
the official POV-Ray binaries could have been built at all?
Christoph
--
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 06 Jul. 2004 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> If you don't know the reason for the compile error you get it is quite
> unreasonable to assume this could be a bug in POV-Ray. If such an
> error was caused by a problem in the POV-Ray source how do you imagine
> that the official POV-Ray binaries could have been built at all?
Yes, we all know that if a piece of software compiles on one Unix-like
platform it is guaranteed to compile on all Unix-like platforms.
Or maybe not. Maybe if you compile software quite often, and it usually
works, and PoV doesn't, it is reasonable to go and ask the PoV-team what
is different that makes it break. Maybe it is a fault with a compilation
tool, or maybe a bug in PoV itself, or maybe just an out-of-date version
of something, but even if it's not a bug in PoV it's still worth
reporting it if only so other people with the same problem can find out
about it.
And Tim, if it's any consolation, it isn't at all obvious to me either.
Daniel
--
Misinformation followed us like a plague You can beat us with wires
Nobody knew from time to time You can beat us with chains
If the plans had changed You can run out your rules but you know
.: www.doublezero.uklinux.net :. You can't outrun the history train
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
