On 20/3/2024 03:23, Riccardo Mottola wrote:
Hi,
Joshua Root wrote:
And this is where it happened. Since this is not a full debug build,
there is no line number information, but you at least know which
method is doing the bad memory access.
But it should be a debug build. Well a build with
Well, “involved” perhaps was too much of a statement, I meant we communicated
on the matter and it was/is work-in-progress to make it work on PowerPC.
We got White Star (Palemoon) building on ppc not long ago btw, but it does not
yet run.
P. S. I should change my Gmail settings, otherwise I’m
Hi,
Sergio Had wrote:
Could you refer me to the beginning of this discussion please?
it started on the Mac Users mailing list, you can find in the archives!
I am also involved in AF project:)
Oh, I am curious, how?
I am essentially the only active developer currently, except Roy who
Hi,
Joshua Root wrote:
(Moving to macports-dev as it is a better fit for this topic.)
indeed, it is a development issue, although well, not for a MacPorts
package (yet?) but use of MP development tools.
Issues that only appear at higher optimisation levels also often
involve undefined
Could you refer me to the beginning of this discussion please?
I am also involved in AF project :)
> On Mar 19, 2024, at 10:11 AM, Joshua Root wrote:
>
> (Moving to macports-dev as it is a better fit for this topic.)
>
> On 18/3/2024 22:50, Riccardo Mottola wrote:
>> I will do another
(Moving to macports-dev as it is a better fit for this topic.)
On 18/3/2024 22:50, Riccardo Mottola wrote:
I will do another compilation reducing the optimization level. GCC has
an issue where beyond gcc6 certain optimizations need to be disabled, or
AF crashes.
Issues that only appear at
