Possible troubleshooting activities I am thinking about:
- Checking the output of
envto see if there might be incorrect python or architecture environment variables set. Something telling uv/python that it is an Intel system or to use Intel binaries. Or to check if there are any Conda/Anaconda/Miniconda variables set, suggesting that there is some conda variety installed and interfering. - Checking the PATH (
echo $PATH) to see if there might be something incorrectly ahead in the path. (But, I think this is unlikely sincewhich install_name_toolindicates that the correct file is being run?) Or, again to see if there might be a conda variety installed and being used. - Uninstalling existing Command Line Tools files and then re-installing Command Line Tools, which seemed to help someone, per Shadowed `install_name_tool` can break Python installation · Issue #14843 · astral-sh/uv · GitHub
I need to think a bit more about it…
Edit: added:
Other possible troubleshooting activities:
- Re-run that failing
uvcommand, but this time add--verboseto the command flags to see if any useful information is printed before the failure. - There exists a
/Users/username/.cache/uvcache folder. Perhaps deleting the cache might help?