macOS – Fix ‘Wine: Command Not Found’ Error After Installing Wine

command linemacoswine

I have installed wine through a .pkg from here. Wine Stable.app works fine, but when I run any wine-related command from the terminal, I get command not found.

Best Answer

The wine related commands are not in the path so you have to add them:

(this is for if you installed it for all users, if it's for only your user put ~/Applications instead of /Applications)

sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/wine /usr/local/bin/wine
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/winecfg /usr/local/bin/winecfg
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/msiexec /usr/local/bin/msiexec

If you installed 64-bit wine also: sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/wine64 /usr/local/bin/wine64

Optional:

sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/notepad /usr/local/bin/notepad
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/regedit /usr/local/bin/regedit
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/regsvr32 /usr/local/bin/regsvr32
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/wineboot /usr/local/bin/wineboot
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/wineconsole /usr/local/bin/wineconsole
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/winedbg /usr/local/bin/winedbg
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/winefile /usr/local/bin/winefile
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/winepath /usr/local/bin/winepath
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/wineserver /usr/local/bin/wineserver
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/start/bin/appdb /usr/local/bin/appdb
sudo ln -s /Applications/Wine\ Stable.app/Contents/Resources/wine/bin/winehelp /usr/local/bin/winehelp

Related Solutions

Terminal Automation – Using ffmpeg in Automator Shell Script vs. Command Line

The Automator script does not automatically share your Terminal.app profile. Paths to additional tools may not be found because Automator's script can not find them.

Try expanding your script to include the absolute or full path to the ffmpeg you want to use:

for f in "$@"
do
    /opt/local/bin/ffmpeg -i "$f" -c:v copy -c:a aac -b:a 384k -strict -2 "${f%.*}.m4v"
done

Alternatively, bring in your Terminal.app profile using the approach to this question, My Automator Workflow fails because it fails to find the git command within the 'Run Shell Script' command? Need help.

MacOS – Brew says Wine is installed but it fails to run with “command not found” error

If it is a simple problem then brew unlink wine and brew link wine might resolve it. This isn't the same as uninstalling and reinstalling, which would be brew remove wine and brew install wine. It should be quite quick.

When brew installs a piece of software it installs it to /usr/local/Cellar and then links it to /usr/local/bin. Unlinking just removes those links, so it is still there but basically sitting somewhere it wouldn't normally be found.

But the first thing to try would be to check that /usr/local/bin is in your path. You can check this by typing echo $PATH in a Terminal window. You should see something like /usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin.

Best Answer

Related Solutions

Terminal Automation – Using ffmpeg in Automator Shell Script vs. Command Line

MacOS – Brew says Wine is installed but it fails to run with “command not found” error

Related Question