POV-Ray : Newsgroups : povray.binaries.images : unexplained : Re: unexplained Server Time
6 Oct 2024 06:24:47 EDT (-0400)
  Re: unexplained  
From: James Holsenback
Date: 16 Aug 2014 08:00:19
Message: <53ef47d3@news.povray.org>
On 08/16/2014 06:49 AM, James Holsenback wrote:
> 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).
>
> have you been able to (or are you even going to) look into why the
> implementation (re-factoring???) of this construct isn't compatible with
> my compiler (that's what appears to be happening) since you can't
> confirm on your end.
>
> it /really/ appears that this (OTOTest file) got broken @
> cf1c3fbedb33802bd431acac43ce41db55fa87b8 and that the issue #29 commits
> just cleaned up the implementation so i could at least compile.
>

following up on the notion that it's compiler/configure related, I did a 
comparison of configure output the buildbot server and my system!

This 1st output is from the buildbot server ...

gcc (Ubuntu/Linaro 4.8.1-10ubuntu9) 4.8.1:

Just a few entries of interest here /not/ all of them ... compare them 
with below output!

Language constructs and functions
---------------------------------
checking size of int... 4
checking size of long int... 8
checking size of size_t... 8
checking size of float... 4

Floating Point Features
-----------------------
checking limits usability... yes
checking limits presence... yes
checking for limits... yes
checking whether NaNs are supported... yes
checking cmath usability... yes
checking cmath presence... yes
checking for cmath... yes
checking whether NaNs can be identified using std::isnan()... no
checking whether NaNs can be identified using global isnan()... no
checking whether NaNs can be identified by comparison to themselves... no
checking whether infinite values are supported... yes
checking for cmath... (cached) yes
checking whether infinities can be identified using std::isinf()... no
checking whether infinities can be identified using global isinf()... no
checking whether infinities can be identified by comparison to the 
maximum value... yes

------

This output is from my system ...

gcc (SUSE Linux) 4.6.2:

Compare to above buildbot output ...

Language constructs and functions
---------------------------------
checking size of int... 4
checking size of long int... 4
checking size of size_t... 4
checking size of float... 4

Did /not/ even have "Floating Point Features" section on my system!!!

The plot thickens? mkl?


Post a reply to this message

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