rwxr-xr-x 1 root wheel 159K Sep 5 22:51 bitcode_strip* rwxr-xr-x 1 root wheel 216K Sep 5 22:51 bison* rwxr-xr-x 1 root wheel 27K Sep 5 22:51 asa* rwxr-xr-x 1 root wheel 40K Sep 5 22:51 as* rwxr-xr-x 1 root wheel 41K Sep 5 22:51 ar* rwxr-xr-x 1 root wheel 32K Sep 5 22:51 SplitForks*

rwxr-xr-x 1 root wheel 31K Sep 5 22:51 SetFile* rwxr-xr-x 1 root wheel 126K Sep 5 22:51 Rez* rwxr-xr-x 1 root wheel 33K Sep 5 22:51 ResMerger* rwxr-xr-x 1 root wheel 31K Sep 5 22:51 GetFileInfo* rwxr-xr-x 1 root wheel 116K Sep 5 22:51 DeRez* /Library/Frameworks/amework/Versions/3.7/bin/2to3

Testing my theory, I probe the folder structure with ls (I should have done this before using the install command): ls ls -la /Library/Developer/CommandLineTools/usr/bin/ĭrwxr-xr-x 124 root wheel 3.9K Oct 28 23:03. (Or it could have made links to the new folder path). Using the install command worked for me, but it is not clear whether this simply downloaded and unpacked files and then skipped installation and simply updated an environment variable or whether it physically installed the files at the expected path.

It seems that upgrading from one MacOS version to another either uninstalls some dev tools or it moves them to another path, and this breaks compatibility with any tool using the environment variable that points to the old location where the tools were located. Invalid active developer path on MAC OS X after installing Ruby

Exiftool mac os x