POV-Ray : Newsgroups : povray.beta-test : problem with +D option at specific output file dimensions : Re: problem with +D option at specific output file dimensions Server Time
30 Apr 2024 17:23:53 EDT (-0400)
  Re: problem with +D option at specific output file dimensions  
From: James Holsenback
Date: 13 Dec 2013 15:27:00
Message: <52ab6d94$1@news.povray.org>
On 12/13/2013 02:24 PM, Le_Forgeron wrote:
> Le 13/12/2013 18:34, James Holsenback nous fit lire :
>> On 12/13/2013 11:37 AM, James Dietrich wrote:
>>> I thought I would try compiling a version with debug symbols in the
>>> hopes of
>>> getting a meaningful backtrace, but was unable to do so.
>>>
>>> I ran ./configure this way:
>>> ../configure --enable-debug --disable-optimiz COMPILED_BY="James Dietrich
>>> <my_email@address>"
>>> and the compilation process eventually failed with this:
>>
>> <snip>
>>
>>> If someone can help me with this, I'll be glad to try again to create
>>> a better
>>> backtrace, if that would be helpful.
>>
>> try adding LIBS="-lboost_system -lboost_thread" at configure time
>>
> Wrong suggestion... IMVHO.

Yep ... concur

>
> The issue is tied to boost not liking the -O0 when handling the
> Gregorian calendar (and the use of some version of g++)... Boost used to
> have the opposite issue: not allowing Gregorian date with gcc 4.3 and
> optimization above -O0. (corrected in 1.38 of boost).
>
> Unless the suggestion by James worked, I would suggest doing (for the
> purpose of getting a binary with previous option) to edit metadata.h
> (source/base/image) to hard code the date and related function.
> (and removing the "boost::gregorian::date              date;" member)

Now that you mention it this has been brought up before. Sheesh ... I'm 
gettin' old


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.