Re: macOS status

"Kirill A. Korinsky" <[email protected]> Sun, 24 Dec 2023 16:20:38 +0100

Newsgroups	gmane.lisp.gcl.devel
Message-ID	<[email protected]>

Hello,

Seems that support of arm64 macOS requires some work at relocation. Just comparing of reloc.h between two arch points that it is quite different:
 - https://github.com/phracker/MacOSX-SDKs/blob/master/MacOSX11.3.sdk/usr/include/mach-o/x86_64/reloc.h <https://github.com/phracker/MacOSX-SDKs/blob/master/MacOSX11.3.sdk/usr/include/mach-o/x86_64/reloc.h>
 - https://github.com/phracker/MacOSX-SDKs/blob/master/MacOSX11.3.sdk/usr/include/mach-o/arm64/reloc.h <https://github.com/phracker/MacOSX-SDKs/blob/master/MacOSX11.3.sdk/usr/include/mach-o/arm64/reloc.h>

--
wbr, Kirill

> On 24. Dec 2023, at 15:40, Kirill A. Korinsky <[email protected]> wrote:
> 
> Hello,
> 
>> On 24. Dec 2023, at 15:37, Camm Maguire <[email protected]> wrote:
>> 
>>> 
>>> Anyway, failed on build; crash happened inside siLheap_report which is called by the first (init-system) at ./raw_pre_gcl
>> 
>> Is this heap report issue the same as your segmentation catcher signal
>> unblocking issue and limited to arm64 alone?
> 
> yes, removing segmentation catcher signal allows to see it. Without it, it simple fails with error in console without any trace.
> 
> FYI: it isn't arm64 build, because configure script doesn't support it. I use so-called Rosetta to run x86_64 binary on arm64 which usually works quite well.
> 
> --
> wbr, Kirill
>

signature.asc (application/pgp-signature, 833 B)