• Dmitry Olshansky (10/10) Jun 16 2023 So I've got my hands on one of 'em MacPros. Great machine, nice
• Steven Schveighoffer (9/19) Jun 16 2023 Yep.
• Dmitry Olshansky (3/14) Jun 16 2023 Yes, thanks that did the trick!
• Dave P. (7/26) Jun 16 2023 That process is too annoying to me. I usually just remove the
• Guillaume Piolat (3/13) Jun 17 2023 Right click on the executable and select "open" then pass the

Dmitry Olshansky <dmitry.olsh gmail.com> writes:

So I've got my hands on one of 'em MacPros. Great machine, nice 
build quality.

Next order of business is to run D on the box, so I've downloaded 
universal binaries off ldc's release page. When I try to run any 
of the binaries nasty message box comes out to tell me it doesn't 
recognise the author of the binary. Any attempt to bypass the 
message turns to failure for me.

Any advice from MacOS users?

---
Dmitry Olshansky

Steven Schveighoffer <schveiguy gmail.com> writes:

On 6/16/23 11:56 AM, Dmitry Olshansky wrote:
 So I've got my hands on one of 'em MacPros. Great machine, nice build 
 quality.
 
 Next order of business is to run D on the box, so I've downloaded 
 universal binaries off ldc's release page. When I try to run any of the 
 binaries nasty message box comes out to tell me it doesn't recognise the 
 author of the binary. Any attempt to bypass the message turns to failure 
 for me.
 
 Any advice from MacOS users?

Yep.

Go into settings, then privacy and security. Make sure "App store and 
identified developers" is checked.

On that page, you will see probably a thing saying "you tried to run 
ldc2 but I blocked it". Say "allow anyway".

Then try it again. This time, it will still block it, but ask you if you 
want to run it.

-Steve

Dmitry Olshansky <dmitry.olsh gmail.com> writes:

On Friday, 16 June 2023 at 16:14:19 UTC, Steven Schveighoffer 
wrote:
 On 6/16/23 11:56 AM, Dmitry Olshansky wrote:
 
 Any advice from MacOS users?

 Yep.

 Go into settings, then privacy and security. Make sure "App 
 store and identified developers" is checked.

 On that page, you will see probably a thing saying "you tried 
 to run ldc2 but I blocked it". Say "allow anyway".

 Then try it again. This time, it will still block it, but ask 
 you if you want to run it.

Yes, thanks that did the trick!

 -Steve

Dave P. <dave287091 gmail.com> writes:

On Friday, 16 June 2023 at 16:25:35 UTC, Dmitry Olshansky wrote:
 On Friday, 16 June 2023 at 16:14:19 UTC, Steven Schveighoffer 
 wrote:
 On 6/16/23 11:56 AM, Dmitry Olshansky wrote:
 
 Any advice from MacOS users?

 Yep.

 Go into settings, then privacy and security. Make sure "App 
 store and identified developers" is checked.

 On that page, you will see probably a thing saying "you tried 
 to run ldc2 but I blocked it". Say "allow anyway".

 Then try it again. This time, it will still block it, but ask 
 you if you want to run it.

 Yes, thanks that did the trick!

 -Steve


That process is too annoying to me. I usually just remove the 
quarantine attribute instead.

```bash
$ xattr -r -d com.apple.quarantine 
ldc2-1.33.0-beta2-osx-universal.tar.xz
```

Guillaume Piolat <first.last spam.org> writes:

On Friday, 16 June 2023 at 15:56:30 UTC, Dmitry Olshansky wrote:
 So I've got my hands on one of 'em MacPros. Great machine, nice 
 build quality.

 Next order of business is to run D on the box, so I've 
 downloaded universal binaries off ldc's release page. When I 
 try to run any of the binaries nasty message box comes out to 
 tell me it doesn't recognise the author of the binary. Any 
 attempt to bypass the message turns to failure for me.

 Any advice from MacOS users?

 ---
 Dmitry Olshansky

Right click on the executable and select "open" then pass the 
popup, next time it is executed it will run from the cmdline.