Oldes / Rebol-issues

Issue tracker for https://github.com/oldes/Rebol3
4 stars 0 forks source link

Regression #2610

Closed ldci closed 4 months ago

ldci commented 4 months ago

Some modules such as blend2D do not work with Rebol3-3.18.0 version.

ldci commented 4 months ago

OK problem corrected with your version 👍

ldci commented 4 months ago

No problem when using your https://github.com/Oldes/Rebol3/releases/download/3.18.0/rebol3-bulk-macos-arm64.gz. Don't work when I'm using sources and siskin .

ldci commented 4 months ago

Problem solved : macOS codesign. I've to desactivate export SISKIN_SIGN_IDENTITY=DEF212C364479537542FEB630620CDE0C7CECAD3in my .profile when compiling your sources with siskin

Oldes commented 4 months ago

The issue probably is, that all my builds are signed with my (personal) developer's identity, which your system don't know and so probably don't trust.. or application signed with my identity don't trust an extension, which you build yourself and is signed with yours (if you have SISKIN_SIGN_IDENTITY defined).

Possible solution is to resign my binaries you use with your identity with command like:

/usr/bin/codesign --force -s $MACOS_IDENTITY_ID ./tree/rebol/Rebol/build/rebol3-base-macos-x64 -v

Where MACOS_IDENTITY_ID would be your identity which is probably DEF212C364479537542FEB630620CDE0C7CECAD3 So in your case the command would be:

/usr/bin/codesign --force -s DEF212C364479537542FEB630620CDE0C7CECAD3 ./tree/rebol/Rebol/build/rebol3-base-macos-x64 -v
Oldes commented 4 months ago

Just for a record, one can use this command to find personal signing identities:

security find-identity -v -p codesigning