-
| 
        
 My friend's M1 Macbook with Big Sur can run the rest of Positron normally, but not for ark. However, my custom version of ark that explicitly sets target through the following lines in the GitHub Workflow does work for her:             - name: Set macOS 11 deployment target
              run: |
                echo "MACOSX_DEPLOYMENT_TARGET=11" >> $GITHUB_ENV
                echo "RUSTFLAGS=-C link-args=-mmacosx-version-min=11" >> $GITHUB_ENVI initially brought this query in #3732 (comment), but I don't think my issue belongs there. I think my issue is akin to #3812 but that was closed in favour of #3732. I also believe my PR posit-dev/ark#946 was closed too early. If 10.15 is no longer officially supported by Positron, I think shifting the minimum support to 11 is fair as that's the "official" minimum version for Mac.  | 
  
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
| 
         hmm indeed I now see the problem. The whole binary has been linked with the correct minos target: But I see that ZeroMQ, our main (or only?) dependency that uses C++, has several object files compiled with a very recent minos target: If I build with: I get the expected: As I understand it's fine to have   | 
  
Beta Was this translation helpful? Give feedback.

hmm indeed I now see the problem. The whole binary has been linked with the correct minos target:
But I see that ZeroMQ, our main (or only?) dependency that uses C++, has several object files compiled with a very recent minos target: