> On Mar 5, 2023, at 3:56 AM, Jonas Maebe via fpc-pascal
> wrote:
>
> There is no need anymore to start with ppcx64 now that there is a native
> ppca64 in the latest FPC release (3.2.2). So you can start directly with your
> step 3 (removing the "FPC=$PWD/ppca64" so it uses the globally inst
On 04/03/2023 07:24, Hairy Pixels via fpc-pascal wrote:
# 1. Compile a native AArch64 compiler from the FPC trunk source
make distclean
make FPC=ppcx64 OPT="-ap -FD${TOOLCHAIN} -XR${MACOS_SDK}" CPU_TARGET=aarch64 -j 4
FPMAKEOPT="-T 4" all
There is no need anymore to start with ppcx64 now that
> On Mar 4, 2023, at 9:10 PM, Hairy Pixels wrote:
>
> Thanks, I’ve done that and here’s both the LLDB output and sample.
>
> It looks like it’s crashed on an exception but I don’t understand why it’s
> spinning the CPU. Either way something is clearly wrong and I’ve never seen
> this before.
> On Mar 4, 2023, at 6:28 PM, Jonas Maebe via fpc-pascal
> wrote:
>
> You can add "-Xs- -gw -Xg" to OPT to prevent symbol stripping and add debug
> info, and then when it's stuck either attach a debugger or run "sample ppcx64"
Thanks, I’ve done that and here’s both the LLDB output and sample
On 04/03/2023 07:24, Hairy Pixels via fpc-pascal wrote:
Here’s the build command I used and it builds the compiler up to step #2 but then
when it copies the compiler to compiler/ppca64 things fall apart. I noticed the
following command "make distclean” stalled out at some point so I tried to ru
Following up I’m trying to rebuild my compiler from sources and something
strange has happened.
Here’s the build command I used and it builds the compiler up to step #2 but
then when it copies the compiler to compiler/ppca64 things fall apart. I
noticed the following command "make distclean” st
