Am 12.08.2014 19:53, schrieb James Holsenback:
> On 08/12/2014 01:41 PM, clipka wrote:
>> Am 12.08.2014 19:08, schrieb James Holsenback:
>>
>>> found OTOTest.pov file laying around in some obscure corner ... here's
>>> results
>>
>> Well, what can I say, other than "I can't reproduce it"?
>>
>> Unless you can trim down the thing to an extremely minimalistic scene
>> (say, one or two primitives with one or two textures) that is rendered
>> differently by the builds you're using, or can nail down exactly what
>> GitHub commit broke it, I might be able to do some guessing; but until
>> then, unfortunately it looks like I need you to do more experimenting.
>>
> well it's after 3.7-stable for sure ...

Thanks for the help, you just narrowed it down to a meagre 120-130 
commits :-)


> OTOc.inc sources math.inc dunno
> if that could be a clue.

I hadn't thought of include files, and it would seem a tempting 
explanation, as I'm not regularly updating my installed set of those; 
but a quick check reveals that I'm already using the newest; which is 
not too surprising, giving that only three changes have been made within 
the include directory since 3.7-stable so far, and none of them seems 
anywhere close to being a plausible candidate. (And no, math.inc hasn't 
been changed at all.)

Post a reply to this message

On 08/12/2014 02:42 PM, clipka wrote:
> Am 12.08.2014 19:53, schrieb James Holsenback:
>> On 08/12/2014 01:41 PM, clipka wrote:
>>> Am 12.08.2014 19:08, schrieb James Holsenback:
>>>
>>>> found OTOTest.pov file laying around in some obscure corner ... here's
>>>> results
>>>
>>> Well, what can I say, other than "I can't reproduce it"?
>>>
>>> Unless you can trim down the thing to an extremely minimalistic scene
>>> (say, one or two primitives with one or two textures) that is rendered
>>> differently by the builds you're using, or can nail down exactly what
>>> GitHub commit broke it, I might be able to do some guessing; but until
>>> then, unfortunately it looks like I need you to do more experimenting.
>>>
>> well it's after 3.7-stable for sure ...
>
> Thanks for the help, you just narrowed it down to a meagre 120-130
> commits :-)

narrowed a bit further ... this hash works fine: 
9a278c7f02003b7e6d6d0665c37695351cb23a27 so something after that!!!!

Post a reply to this message

On 08/12/2014 02:55 PM, James Holsenback wrote:
> On 08/12/2014 02:42 PM, clipka wrote:
>> Am 12.08.2014 19:53, schrieb James Holsenback:
>>> On 08/12/2014 01:41 PM, clipka wrote:
>>>> Am 12.08.2014 19:08, schrieb James Holsenback:
>>>>
>>>>> found OTOTest.pov file laying around in some obscure corner ... here's
>>>>> results
>>>>
>>>> Well, what can I say, other than "I can't reproduce it"?
>>>>
>>>> Unless you can trim down the thing to an extremely minimalistic scene
>>>> (say, one or two primitives with one or two textures) that is rendered
>>>> differently by the builds you're using, or can nail down exactly what
>>>> GitHub commit broke it, I might be able to do some guessing; but until
>>>> then, unfortunately it looks like I need you to do more experimenting.
>>>>
>>> well it's after 3.7-stable for sure ...
>>
>> Thanks for the help, you just narrowed it down to a meagre 120-130
>> commits :-)
>
> narrowed a bit further ... this hash works fine:
> 9a278c7f02003b7e6d6d0665c37695351cb23a27 so something after that!!!!
>
>
ok so at hash 54b283a0d39c637ce9d4ab16512a364e993c58c5 its busted so I 
think that's considerable less territory to cover.

Post a reply to this message

Le 12/08/2014 19:48, clipka a écrit :
> Am 12.08.2014 19:34, schrieb James Holsenback:
> 
>> I stayed out of my local git repos as I've made some changes ... Instead
>> downloaded the zip package made available from povray github with the
>> master filter selected, it has this hash
>> ad6d545729bbd92800fc2d65fe74dcac86408c27 and has the problem.
> 
> That's 3.7.1-alpha.7681813, so same version as I used.
> 
>> With 3.7-stable filter set, this hash
>> 39ce8a24e50651904010dda15872d63be15d7c37 tis ok fine
> 
> That's the genuine 3.7.0 release proper, aka "3.7.0 stable".
> 
Yet another compiler issue ?

Is there a full-scene available for download and test ?

-- 
Just because nobody complains does not mean all parachutes are perfect.

Post a reply to this message

On 08/13/2014 03:16 AM, Le_Forgeron wrote:
> Le 12/08/2014 19:48, clipka a écrit :
>> Am 12.08.2014 19:34, schrieb James Holsenback:
>>
>>> I stayed out of my local git repos as I've made some changes ... Instead
>>> downloaded the zip package made available from povray github with the
>>> master filter selected, it has this hash
>>> ad6d545729bbd92800fc2d65fe74dcac86408c27 and has the problem.
>>
>> That's 3.7.1-alpha.7681813, so same version as I used.
>>
>>> With 3.7-stable filter set, this hash
>>> 39ce8a24e50651904010dda15872d63be15d7c37 tis ok fine
>>
>> That's the genuine 3.7.0 release proper, aka "3.7.0 stable".
>>
> Yet another compiler issue ?

I'm having my suspicions that is what's going on ...

>
> Is there a full-scene available for download and test ?
>

Yep ... the OTOTest.pov file that comes with the OTOc.inc package (over 
in p.b.scene-files

Post a reply to this message

On 08/12/2014 03:53 PM, James Holsenback wrote:
> On 08/12/2014 02:55 PM, James Holsenback wrote:
>> On 08/12/2014 02:42 PM, clipka wrote:
>>> Am 12.08.2014 19:53, schrieb James Holsenback:
>>>> On 08/12/2014 01:41 PM, clipka wrote:
>>>>> Am 12.08.2014 19:08, schrieb James Holsenback:
>>>>>
>>>>>> found OTOTest.pov file laying around in some obscure corner ...
>>>>>> here's
>>>>>> results
>>>>>
>>>>> Well, what can I say, other than "I can't reproduce it"?
>>>>>
>>>>> Unless you can trim down the thing to an extremely minimalistic scene
>>>>> (say, one or two primitives with one or two textures) that is rendered
>>>>> differently by the builds you're using, or can nail down exactly what
>>>>> GitHub commit broke it, I might be able to do some guessing; but until
>>>>> then, unfortunately it looks like I need you to do more experimenting.
>>>>>
>>>> well it's after 3.7-stable for sure ...
>>>
>>> Thanks for the help, you just narrowed it down to a meagre 120-130
>>> commits :-)
>>
>> narrowed a bit further ... this hash works fine:
>> 9a278c7f02003b7e6d6d0665c37695351cb23a27 so something after that!!!!
>>
>>
> ok so at hash 54b283a0d39c637ce9d4ab16512a364e993c58c5 its busted so I
> think that's considerable less territory to cover.

this hash ac564f7231f2b05b461a3a03fe6b9ed21b845c5a is the last working 
commit (compiles and runs OTOTest.pov properly)

broken @ cf1c3fbedb33802bd431acac43ce41db55fa87b8 ... doesn't even 
compile ./base/safemath.h is belching errors all over the place

In file included from base/image/image.cpp:57:0:



scope
./base/safemath.h:51:2: note: suggested alternative:













./base/safemath.h:61:33: note: candidates are:
/usr/include/c++/4.6/bits/stl_algobase.h:254:5: note: template<class 
_Tp, class _Compare> const _Tp& std::max(const _Tp&, const _Tp&, _Compare)
/usr/include/c++/4.6/bits/stl_algobase.h:210:5: note: template<class 
_Tp> const _Tp& std::max(const _Tp&, const _Tp&)
make[2]: *** [base/image/image.o] Error 1

Post a reply to this message

Am 13.08.2014 12:11, schrieb James Holsenback:

>>> narrowed a bit further ... this hash works fine:
>>> 9a278c7f02003b7e6d6d0665c37695351cb23a27 so something after that!!!!
>>>
>>>
>> ok so at hash 54b283a0d39c637ce9d4ab16512a364e993c58c5 its busted so I
>> think that's considerable less territory to cover.
>
> this hash ac564f7231f2b05b461a3a03fe6b9ed21b845c5a is the last working
> commit (compiles and runs OTOTest.pov properly)
>
> broken @ cf1c3fbedb33802bd431acac43ce41db55fa87b8 ... doesn't even
> compile ./base/safemath.h is belching errors all over the place

Ah, yes, that one... that's part of GitHub issue #29. It'll need 
replacing of "numeric_limits" with "std::numeric_limits" (and then 
probably some more fixes).

Post a reply to this message

On 13/08/2014 10:26, James Holsenback wrote:
> On 08/13/2014 03:16 AM, Le_Forgeron wrote:
>> Le 12/08/2014 19:48, clipka a écrit :
>>> Am 12.08.2014 19:34, schrieb James Holsenback:
>>>
>>>> I stayed out of my local git repos as I've made some changes ...
>>>> Instead
>>>> downloaded the zip package made available from povray github with the
>>>> master filter selected, it has this hash
>>>> ad6d545729bbd92800fc2d65fe74dcac86408c27 and has the problem.
>>>
>>> That's 3.7.1-alpha.7681813, so same version as I used.
>>>
>>>> With 3.7-stable filter set, this hash
>>>> 39ce8a24e50651904010dda15872d63be15d7c37 tis ok fine
>>>
>>> That's the genuine 3.7.0 release proper, aka "3.7.0 stable".
>>>
>> Yet another compiler issue ?
> 
> I'm having my suspicions that is what's going on ...
> 

Identify your compiler ?
mine is gcc 4.8.2 (ubuntu) and testing with
ad6d545729bbd92800fc2d65fe74dcac86408c27 (head of master), it works ok here.
(from OTOC... )

(I did not reinstall the include files, so changes in such files might
not be reflected)


>>
>> Is there a full-scene available for download and test ?
>>
> 
> Yep ... the OTOTest.pov file that comes with the OTOc.inc package (over
> in p.b.scene-files
> 
Thanks.

-- 
IQ of crossposters with FU: 100 / (number of groups)
IQ of crossposters without FU: 100 / (1 + number of groups)
IQ of multiposters: 100 / ( (number of groups) * (number of groups))

Post a reply to this message

On 08/13/2014 04:07 PM, Le_Forgeron wrote:
> On 13/08/2014 10:26, James Holsenback wrote:
>> On 08/13/2014 03:16 AM, Le_Forgeron wrote:
>>> Le 12/08/2014 19:48, clipka a écrit :
>>>> Am 12.08.2014 19:34, schrieb James Holsenback:
>>>>
>>>>> I stayed out of my local git repos as I've made some changes ...
>>>>> Instead
>>>>> downloaded the zip package made available from povray github with the
>>>>> master filter selected, it has this hash
>>>>> ad6d545729bbd92800fc2d65fe74dcac86408c27 and has the problem.
>>>>
>>>> That's 3.7.1-alpha.7681813, so same version as I used.
>>>>
>>>>> With 3.7-stable filter set, this hash
>>>>> 39ce8a24e50651904010dda15872d63be15d7c37 tis ok fine
>>>>
>>>> That's the genuine 3.7.0 release proper, aka "3.7.0 stable".
>>>>
>>> Yet another compiler issue ?
>>
>> I'm having my suspicions that is what's going on ...
>>
>
> Identify your compiler ?

gcc (SUSE Linux) 4.6.2

> mine is gcc 4.8.2 (ubuntu) and testing with
> ad6d545729bbd92800fc2d65fe74dcac86408c27 (head of master), it works ok here.
> (from OTOC... )
>
> (I did not reinstall the include files, so changes in such files might
> not be reflected)
>
>
>>>
>>> Is there a full-scene available for download and test ?
>>>
>>
>> Yep ... the OTOTest.pov file that comes with the OTOc.inc package (over
>> in p.b.scene-files
>>
> Thanks.
>

Post a reply to this message

On 08/13/2014 07:28 AM, clipka wrote:
> Am 13.08.2014 12:11, schrieb James Holsenback:
>
>>>> narrowed a bit further ... this hash works fine:
>>>> 9a278c7f02003b7e6d6d0665c37695351cb23a27 so something after that!!!!
>>>>
>>>>
>>> ok so at hash 54b283a0d39c637ce9d4ab16512a364e993c58c5 its busted so I
>>> think that's considerable less territory to cover.
>>
>> this hash ac564f7231f2b05b461a3a03fe6b9ed21b845c5a is the last working
>> commit (compiles and runs OTOTest.pov properly)
>>
>> broken @ cf1c3fbedb33802bd431acac43ce41db55fa87b8 ... doesn't even
>> compile ./base/safemath.h is belching errors all over the place
>
> Ah, yes, that one... that's part of GitHub issue #29. It'll need
> replacing of "numeric_limits" with "std::numeric_limits" (and then
> probably some more fixes).
>
>
went to #af80da48a650b51039d23318a73b583493d81200 (last of #29 issue) 
and now it builds clean, but the wall from the OTO test scene is incomplete

Post a reply to this message