On 11/10/25 04:52, jr wrote:
> hi,
> 
> William F Pokorny <ano### [at] anonymousorg> wrote:
>> ...
>> 2) Both the default unix build and the build script jr provided use
>> -ffast-math. There are a number of flaky fails due recent compiler
>> changes to what -ffast-math does. Change that flag to: -fno-fast-math or
>> add the flag -fno-finite-math-only to your CXXFLAGS and try another build.
> 
> in light of yesbird asking whether optimisation should be turned off perhaps, I
> think it would be beneficial if (at least) the build flags for default *NIX were
> appended / updated to include the '-fno-finite-math-only'.  can do ?
> 

No(*), not easily.

---

It's true I did some github things a year or so ago to get bumped to a 
developer with the idea I might do a few quick commits like this, but my 
github upgrade from contributor to developer didn't go well. Best I 
could tell, I ended up with developer permission to one hidden / 
developer only fork / branch about which I know nothing.

None of the automated, github, build, check and release stuff is 
currently working. I never understood that set up beyond checking 
results of the auto-build-check fails. I have now not used github 
itself, except for occasionally commenting on issues posted there, for 
more than 5 years.

I cannot help with or support any windows specific development.

The suggested change should be made in at least 3 github branches. The 
github support infrastructure is really nice when it's all working - but 
even then, the simplest change takes non-trivial 'git / github' time.

---

My Unix/Linux only yuqk fork is different. The Unix build system itself 
is substantially different. I don't even have the --disable-optimiz 
configure option YB used(**) to build on his machine, for example.

---

Lastly, of late, real life is leaving me with much less time for my 
POV-Ray hobby :-(.

Bill P.


(*) - You're likely guessing correctly that YB's core issue comes down 
to the -ffast-math changes. The --disable-optimize option almost 
certainly turns off fast math.

(**) - Completely non-optimized POV-Ray builds are slow. (Though, it is 
a workaround for the gnu compiler optimizations breaking the dynamic cpu 
detection code issue (fixed in yuqk no matter the compiler optimization 
level))

Post a reply to this message

On 11/10/25 06:44, William F Pokorny wrote:
> It's true I did some github things a year or so ago to get bumped to a 
> developer with the idea I might do a few quick commits like this, but my 
> github upgrade from contributor to developer didn't go well. Best I 
> could tell, I ended up with developer permission to one hidden / 
> developer only fork / branch about which I know nothing.

I recently got an email from a friend on this subject. I want to make 
clear I am the one who has not pursued fixing the situation above.

It might be something I could fix myself with some time and focus. If 
not, others - like Chris - would certainly try and help me, but I don't 
want others burning time for something I'm currently unlikely to much 
use(*).

Aside:

Thinking about the patch, it's safer to remove the -ffast-math flag, I 
think. I'm unsure how pervasive the -fno-finite-math-only flag is... 
(clang ?)

Bill P.

(*) - Eventually, I plan to move 'yuqk' to github as I am already using 
git for it locally. At that change I'll be coming up to speed with 
github for yuqk - and sorting base POV-Ray github issues then, should be 
easier.

Post a reply to this message

On 14/11/2025 20:32, William F Pokorny wrote:

> (*) - Eventually, I plan to move 'yuqk' to github as I am already using 
> git for it locally. At that change I'll be coming up to speed with 
> github for yuqk - and sorting base POV-Ray github issues then, should be 
> easier.

Good luck with it - Github is a _very_ useful and now "must have"
service. I can suggest desktop version with excellent GUI:
https://desktop.github.com/download/

There is also a Linux fork, which I am using too, but you will need some
googling to find it.
--
YB

Post a reply to this message