I am not sure which mono 4.x release that started in…īut I would assume that you do not have /usr/local/bin in your path(?), try: export PATH=/usr/local/bin:$ Newer versions of mono comply to the “El Capitan” requirements of not installing anything into /usr/bin and thus now /usr/local/bin is used. So /usr/local/bin is no longer used… Original The latest versions of Mono (5.x) installation process creates a file ( mono-commands) in /etc/paths.d that contains the path of: /Library/Frameworks/amework/Versions/Current/Commands 1: Update (since this is still getting views two+ years later): …but it isn’t present in /usr/bin and attempting to find its executable using which mono returns nothing. Lrwxr-xr-x 1 root wheel 60 Sep 9 22:16 amework -> /System/Library/PrivateFrameworks/ameworkĭrwxr-xr-x 5 root wheel 170 ameworkĭrwxr-xr-x 8 root wheel 272 Sep 9 22:19 amework /Applications/Motion.app/Contents/Frameworks/AudioMi圎ameworkĭrwxr-xr-x 8 root admin 272 Sep 12 11:24 amework Lrwxr-xr-x 1 root wheel 74 AudioMi圎amework ->.
/Applications/Motion.app/Contents/Frameworks/amework The mono framework does appear to be installed: Lees-Mac-Pro:Downloads kevinmack$ cd /Volumes/Macintosh\ HD/Library/Frameworks/
The installer appeared to complete successfully, but an attempt to call mono returns To install it, I ran uninstallMono.sh as root to ensure we didn’t have any leftover cruft, then ran MonoFramework-MDK-4.0.4.1. I’m trying to get a Mono install running on a mac (OS X version 10.10.5), and while the install states that it’s completed successfully, I’m not able to call mono from the terminal.
0 kommentar(er)
