 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
I tried to compile the source code of povray 3.5 in Debug mode using VC++
and it worked fine but it gives an INTERNAL COMPILATION ERROR at different
places in the release mode in files like blob.cpp lighting.cpp
When I turn off all the optimizations then it compiles back. But then
release mode has not meaning.
Anybody has any clue about this problem?
Thanks a lot in advance !
Maurya
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 23 Aug 2003 01:55:16
Message: <3f4701c4$1@news.povray.org>
|
|
|
| |
| |
|
|
In article <web.3f46c4398e69b4cac22240400@news.povray.org> , "Maurya"
<mau### [at] hotmail com> wrote:
> Hi,
> I tried to compile the source code of povray 3.5 in Debug mode using VC++
> and it worked fine but it gives an INTERNAL COMPILATION ERROR at different
> places in the release mode in files like blob.cpp lighting.cpp
>
> When I turn off all the optimizations then it compiles back. But then
> release mode has not meaning.
>
> Anybody has any clue about this problem?
The compiler is defective. Try to install all service packs, maybe it works
better, there is nothing else you can do to fix the compiler your have. It
if still does work, upgrade.
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
|
|
| |
| |
|
|
From: Ben Birdsey
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 12 Feb 2004 13:11:14
Message: <402bc1c2$1@news.povray.org>
|
|
|
| |
| |
|
|
There is a problem with using some optimizations on some of the source
files. You can try different configurations, but using the "omit frame
pointer" or "generate intrinsic functions" are the two that cause the
most problem for me. Plus, a lot of the POV code has aliased variables
(in an attempt to speed up the code) that confuses most compilers, so
you should use the appropriate switches.
Thorsten Froehlich wrote:
> In article <web.3f46c4398e69b4cac22240400@news.povray.org> , "Maurya"
> <mau### [at] hotmailcom> wrote:
>
>
>>Hi,
>>I tried to compile the source code of povray 3.5 in Debug mode using VC++
>>and it worked fine but it gives an INTERNAL COMPILATION ERROR at different
>>places in the release mode in files like blob.cpp lighting.cpp
>>
>>When I turn off all the optimizations then it compiles back. But then
>>release mode has not meaning.
>>
>>Anybody has any clue about this problem?
>
>
> The compiler is defective. Try to install all service packs, maybe it works
> better, there is nothing else you can do to fix the compiler your have. It
> if still does work, upgrade.
>
> 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
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 13 Feb 2004 05:53:19
Message: <402cac9f$1@news.povray.org>
|
|
|
| |
| |
|
|
"Ben Birdsey" <cla### [at] mailcom> schrieb im Newsbeitrag
news:402bc1c2$1@news.povray.org...
> There is a problem with using some optimizations on some of the source
> files.
Sorry, this is plain incorrect. Valid source code cannot result in invalid
compiled program code unless the compiler is defective. And VC 6.0 is
notorious for its bugs. The POV-Ray source code makes no use of undefined
or platform specific properies of C/C++.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 13 Feb 2004 05:59:56
Message: <402cae2c$1@news.povray.org>
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> schrieb im Newsbeitrag
news:402cac9f$1@news.povray.org...
> "Ben Birdsey" <cla### [at] mailcom> schrieb im Newsbeitrag
> news:402bc1c2$1@news.povray.org...
> > There is a problem with using some optimizations on some of the source
> > files.
>
> Sorry, this is plain incorrect.
Of course this statement makes only sense when quoting the whole message,
not just this sentence...
>>>
> There is a problem with using some optimizations on some of the source
> files. You can try different configurations, but using the "omit frame
> pointer" or "generate intrinsic functions" are the two that cause the
> most problem for me. Plus, a lot of the POV code has aliased variables
> (in an attempt to speed up the code) that confuses most compilers, so
> you should use the appropriate switches.
<<<
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
From: Mike Raiford
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 13 Feb 2004 09:33:19
Message: <402ce02f@news.povray.org>
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:402cac9f$1@news.povray.org...
> Sorry, this is plain incorrect. Valid source code cannot result in
invalid
> compiled program code unless the compiler is defective. And VC 6.0 is
> notorious for its bugs. The POV-Ray source code makes no use of undefined
> or platform specific properies of C/C++.
Hm. I've had no problems building POV-Ray on VC6 at all. The program builds
fine, and runs fine. There's obviously something wrong with his
configuration causing the build to fail. I have to wonder if the part he's
trying to build that may be causing the failure is the editor portion which
was meant to be compiled under Borland C++ Builder ...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:402cac9f$1@news.povray.org...
> "Ben Birdsey" <cla### [at] mailcom> schrieb im Newsbeitrag
> news:402bc1c2$1@news.povray.org...
> > There is a problem with using some optimizations on some of the source
> > files.
>
> Sorry, this is plain incorrect. Valid source code cannot result in
invalid
> compiled program code unless the compiler is defective. And VC 6.0 is
> notorious for its bugs. The POV-Ray source code makes no use of undefined
> or platform specific properies of C/C++.
Thorsten is right about compilers not always being up to snuff. However, if
you have applied all of the recent patches to VC 6.0, it has matured into a
stable product. Also, consider MingGW, the free GNU C/C++ compiler for
Windows. It works great!
Post a reply to this message
|
|
| |
| |
|
|
From: Antoine BRUNEL
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 20 Feb 2004 21:39:43
Message: <4036c4ef$1@news.povray.org>
|
|
|
| |
| |
|
|
Hi from Paris
I had the same problem with VC 6.0 professional....
and solved the "internal compiler error" by applying Service Pack 5 for
Visual studio, available at microsoft's downloads.
think easy, think microsoft: apply the patches :-))
news:402bc1c2$1@news.povray.org...
> There is a problem with using some optimizations on some of the source
> files. You can try different configurations, but using the "omit frame
> pointer" or "generate intrinsic functions" are the two that cause the
> most problem for me. Plus, a lot of the POV code has aliased variables
> (in an attempt to speed up the code) that confuses most compilers, so
> you should use the appropriate switches.
>
> Thorsten Froehlich wrote:
>
> > In article <web.3f46c4398e69b4cac22240400@news.povray.org> , "Maurya"
> > <mau### [at] hotmailcom> wrote:
> >
> >
> >>Hi,
> >>I tried to compile the source code of povray 3.5 in Debug mode using
VC++
> >>and it worked fine but it gives an INTERNAL COMPILATION ERROR at
different
> >>places in the release mode in files like blob.cpp lighting.cpp
> >>
> >>When I turn off all the optimizations then it compiles back. But then
> >>release mode has not meaning.
> >>
> >>Anybody has any clue about this problem?
> >
> >
> > The compiler is defective. Try to install all service packs, maybe it
works
> > better, there is nothing else you can do to fix the compiler your have.
It
> > if still does work, upgrade.
> >
> > 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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Mike Raiford" <mra### [at] hotmailcom> wrote:
> "Thorsten Froehlich" <tho### [at] trfde> wrote in message
> news:402cac9f$1@news.povray.org...
>
> > Sorry, this is plain incorrect. Valid source code cannot result in
> invalid
> > compiled program code unless the compiler is defective. And VC 6.0 is
> > notorious for its bugs. The POV-Ray source code makes no use of undefined
> > or platform specific properies of C/C++.
>
> Hm. I've had no problems building POV-Ray on VC6 at all. The program builds
> fine, and runs fine. There's obviously something wrong with his
> configuration causing the build to fail. I have to wonder if the part he's
> trying to build that may be causing the failure is the editor portion which
> was meant to be compiled under Borland C++ Builder ...
is this 3.5 still around?
just how many hours would it take to rewrite 3.6 to VC6 code?
40? 400? 4000?
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: Compiling POVRAY 3.5 using VC6.0 in Release Mode
Date: 26 Nov 2007 11:50:09
Message: <474af941$1@news.povray.org>
|
|
|
| |
| |
|
|
alphaQuad wrote:
> is this 3.5 still around?
<http://www.povray.org/download/> (scroll to the bottom and follow the link)
> just how many hours would it take to rewrite 3.6 to VC6 code?
> 40? 400? 4000?
Please see <http://support.microsoft.com/lifecycle/?p1=3003>. Visual C 6 is
dead and has been officially dead since 9/30/2005. What sense would it make
to dump any resources into rewriting code for a known to be defective
compiler that has been unsupported by its manufacturer for two years? Get
Visual C 7.1 or later and be done with it.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
