[question] code signing on macos big sur #41

Activity

1. gpu commented on Aug 25, 2021

   

   gpu

   on Aug 25, 2021

   Owner

   More actions

   ^{Sorry for the delay here}

   I haven't been aware of the topic of "code signing" at all. Usually, the Mac binaries are provided by external contributors. I hope it is OK to ping @LlemonDuck here: I think you provided the last Mac binaries - do you know details about this topic, or did you do something to "sign" the code in any way?
2. LlemonDuck commented on Aug 25, 2021

   

   LlemonDuck

   on Aug 25, 2021

   Contributor

   More actions

   I did not do any code signing for the natives. However, it was not built for ARM, and should not require code signing since, AFAIK, code signatures are only required for ARM binaries, and not required for Intel binaries. If you are trying to load these binaries through an ARM-executed Java stack, I'm not entirely surprised that it had issues.

   You could try providing an ad-hoc signature to the binary with codesign -s - binary_name, but again, the binary wasn't built for ARM and I don't expect it would execute in the first place under non-Rosetta execution.

   I'm also not even entirely sure that OpenCL will have an ARM implementation on the M1 macs, considering it has been deprecated technology on macOS for a while now. If you really want it to run on M1, you could try building the binaries yourself referencing the OpenCL headers on ARM, if they exist, then codesign locally and try that.
3. gpu commented on Aug 25, 2021

   

   gpu

   on Aug 25, 2021

   Owner

   More actions

   Admittedly, much of this goes way over my head, in terms of specifics for MacOS, ARM and the requirements. There once was a contribution for ARM binaries at #32 (comment) , but this was not part of a release, and I don't know whether it would suffer from the same problem as the linked FFI library. If anybody has further ideas or insights (or maybe even tried out the binary that I linked to), feel free to share them here.