I just found out that I can't build the "Release SSE2"
configuration on my system (which has Visual C++ 2005 Express
Edition plus platform SDK, so it is not an official build
environment).

Still, did someone else experience this problem, maybe also
with the full version of Visual Studio 2005? Are there any
differences between the configurations except for the
BUILD_SSE2 define and the /arch:SSE2 compiler option?

Everything builds fine but the final linking of povwin crashes
with an internal linker error, with some a reference given to inline
operator overloads of the Counter template class in statistics.h.
System is XP SP2 with Pentium 4, "Debug" and "Release" work fine.

This is still with beta 34 sources as I thought I'd jump
right to beta 36 sources when they become available. Anyway,
nothing relevant seems to have changed for beta 35.

BTW, the changelog on http://www.povray.org/beta/ seems
to be missing the changes between 35a and 36.

Post a reply to this message

On 11.04.10 15:35, Christian Froeschlin wrote:
> Everything builds fine but the final linking of povwin crashes
> with an internal linker error, with some a reference given to inline
> operator overloads of the Counter template class in statistics.h.
> System is XP SP2 with Pentium 4, "Debug" and "Release" work fine.

An "internal linker error" is a bug in the linker of Visual Studio causing a 
fatal malfunction of the linker. It is not a bug in POV-Ray! You need to 
contact the vendor of your compiler/linker (Microsoft) to either obtain the 
most current service pack or get a hotfix.

Alternatively, consider moving to a more recent version of the 
compiler/linker, as I am pretty sure Microsoft no longer provides free 
support for Visual Studio 2005. So they might actually charge for hotfixes.

	Thorsten, POV-Team

Post a reply to this message

Thorsten Froehlich wrote:

> An "internal linker error" is a bug in the linker of Visual Studio 
> causing a fatal malfunction of the linker. It is not a bug in POV-Ray! 

I'm aware of that. I was just interested whether other people
had this problem, considering that Microsoft compilers and
linkers (also from Visual Studio 2005) are the preferred
build environment for 3.7 on Windows.

Post a reply to this message

On 11.04.10 17:49, Christian Froeschlin wrote:
> Thorsten Froehlich wrote:
>
>> An "internal linker error" is a bug in the linker of Visual Studio
>> causing a fatal malfunction of the linker. It is not a bug in POV-Ray!
>
> I'm aware of that. I was just interested whether other people
> had this problem, considering that Microsoft compilers and
> linkers (also from Visual Studio 2005) are the preferred
> build environment for 3.7 on Windows.

Hmm, wasn't that VS 2008? (Haven't built the Win version for a few years.) 
Anyway, from my own work experience with VS 2005, without installing the 
service back and a handful of hotfixes it is not that stable, in particular 
when template code (i.e. boost) is concerned. So you might want to check if 
the Express compiler/linker also has a service pack. Or try VS 2008.

	Thorsten

Post a reply to this message

Thorsten Froehlich wrote:

> you might want to check if the Express compiler/linker also has a 
> service pack.

guess what, there is an SP1 for C++ 2005 express and it solved
the problem for me. It's called VS80sp1-KB926748-X86-INTL.exe for
anyone else who tries to locate it.

This might be an interesting bit of information for the 3.7
build instructions, especially if it should apply to the full
edition as well. I think Chris Cason also tests the build
with Visual Studio 2005 but he might have SP1 installed.

Post a reply to this message

Am 11.04.2010 18:39, schrieb Thorsten Froehlich:

>> I'm aware of that. I was just interested whether other people
>> had this problem, considering that Microsoft compilers and
>> linkers (also from Visual Studio 2005) are the preferred
>> build environment for 3.7 on Windows.
>
> Hmm, wasn't that VS 2008? (Haven't built the Win version for a few
> years.) Anyway, from my own work experience with VS 2005, without
> installing the service back and a handful of hotfixes it is not that
> stable, in particular when template code (i.e. boost) is concerned. So
> you might want to check if the Express compiler/linker also has a
> service pack. Or try VS 2008.

To my knowledge, POV-Ray for Windows is supposed to build with both VS 
2005 and VS 2008; I myself use VS 2005, but with SP2, so I can't tell 
how it compiles with "naked" VS 2005.

Post a reply to this message

clipka wrote:

> To my knowledge, POV-Ray for Windows is supposed to build with both VS 
> 2005 and VS 2008; I myself use VS 2005, but with SP2, so I can't tell 
> how it compiles with "naked" VS 2005.

Unless someone steps up to say he compiled the "Release SSE2"
configuration of a current beta on a "naked" VS 2005, it might
be useful to include a non-committal statement under the Visual
Studio 2005 / 2008 /Express sections in the readme at

   http://www.povray.org/beta/source/povwin-src-readme.html

such as

   "It is recommended to install the latest service packs for
   these environments, especially if the build fails with an
   internal compiler or linker error".

Post a reply to this message