[Glass] Starting Seaside in Gemstone/s - MacOS

[Kurt Kilpela]

Graham,

It sounds like something odd is going on on your system. GemStone signs the
macOS releases and they do not appear to be flagged for me. I tested 3.7.1
and 3.7.1 arm64 and i386 builds. Note I ran i386 builds under Rosetta 2.

You may need to change your gatekeeper settings to 'Allow applications from
"App Store & Known Developers"' in order for GemStone to run.

You can also verify the code signing by running `codesign -dv --verbose=4
$GEMSTONE/bin/gslist`.

> I can happily work with Classes in GT and in Gemstone.
>From the sounds of it you are able to run a stone. Are you using the same
$GEMSTONE to start that stone?

Kurt

On Thu, Feb 13, 2025 at 8:37 AM Graham McLeod via Glass <
glass at lists.gemtalksystems.com> wrote:

> Hi
>
> I am trying to get Seaside running directly in Gemstone.
> I have Glamorous Toolkit and gt4Gemstone installed and connected.
> I can happily work with Classes in GT and in Gemstone.
> I have Seaside running in GT.
>
> I want to run Seaside directly in Gemstone.
> I have set environment variables.
>
> When running gslist or startSeaside_Hyper from terminal, I get MacOs
> Errors saying either gslist or Topaz have been blocked from execution as
> they are regarded as unsafe.
> I have run the MacOS commands to recursively un-quarantine files in the
> Gemstone directory, but this has not resolved
> the issue. I am on latest MacOS 15.3 and Gemstone 3.7.1
>
> Please help!
>
> Thanks
> Graham
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> https://lists.gemtalksystems.com/mailman/listinfo/glass
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/archives/glass/attachments/20250213/fb4b9138/attachment.htm>