| Thread overview | |||||||
|---|---|---|---|---|---|---|---|
|
June 16, 2023 Running LDC on a recent MacOS | ||||
|---|---|---|---|---|
| ||||
 | 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 | |||
June 16, 2023 Re: Running LDC on a recent MacOS | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Dmitry Olshansky | 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 | |||
June 16, 2023 Re: Running LDC on a recent MacOS | ||||
|---|---|---|---|---|
| ||||
Posted in reply to Steven Schveighoffer | 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 | |||
June 17, 2023 Re: Running LDC on a recent MacOS | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Dmitry Olshansky | 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. | |||
June 17, 2023 Re: Running LDC on a recent MacOS | ||||
|---|---|---|---|---|
| ||||
 Posted in reply to Dmitry Olshansky | 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. | |||
Permalink
Reply
