[darktable-dev] 3.0.2 for Mac wont start: file system relative paths not allowed in hardened programs

2020-07-01 Thread Ken Ellinwood
This is on OSX 10.15.5 dyld: Library not loaded: @executable_path/../Resources/lib/libepoxy.0.dylib Referenced from: /Applications/darktable.app/Contents/Resources/lib/libgtk-3.0.dylib Reason: no suitable image found. Did find: /Applications/darktable.app/Contents/MacOS/../Resources/lib/libep

Re: [darktable-dev] 3.0.2 for Mac wont start: file system relative paths not allowed in hardened programs

2020-07-01 Thread parafin
errno=13 is EACCES /* Permission denied */ Maybe you have broken permissions on some files. What does the following command show: ls -l /Applications/darktable.app/Contents/MacOS/../Resources/lib/libepoxy.0.dylib On Wed, 1 Jul 2020 07:11:08 -1000 Ken Ellinwood wrote: > This is on OSX 10.15.5 >

Re: [darktable-dev] 3.0.2 for Mac wont start: file system relative paths not allowed in hardened programs

2020-07-01 Thread Ken Ellinwood
$ ls -l /Applications/darktable.app/Contents/MacOS/../Resources/lib/libepoxy.0.dylib -rwxr-xr-x 1 ken.ellinwood admin 1269408 Apr 16 09:23 /Applications/darktable.app/Contents/MacOS/../Resources/lib/libepoxy.0.dylib I don't see a permissions issue. I think the system is complaining that relati

Re: [darktable-dev] 3.0.2 for Mac wont start: file system relative paths not allowed in hardened programs

2020-07-01 Thread parafin
That's how app bundles work, so I'm not sure how it can be forbidden. But maybe it wants @rpath, not @executable_path... Is it reproducible by anyone else? I don't have 10.15 macOS here. On Wed, 1 Jul 2020 09:08:35 -1000 Ken Ellinwood wrote: > $ ls -l > /Applications/darktable.app/Contents/MacO

Re: [darktable-dev] 3.0.2 for Mac wont start: file system relative paths not allowed in hardened programs

2020-07-01 Thread August Schwerdfeger
I have no problem running Darktable 3.0.2 on macOS 10.15.5. -- August Schwerdfeger aug...@schwerdfeger.name On Wed, Jul 1, 2020 at 2:39 PM parafin wrote: > That's how app bundles work, so I'm not sure how it can be forbidden. > But maybe it wants @rpath, not @executable_path... Is it reproducib