The GM release has already disabled the NVRAM workaround, so this answer should get you what you need moving forward.Ītm, the mono framework installer only works correctly if you install it to root. Note: Previous answers around the Internet about this problem give you instructions for modifying NVRAM settings, but Apple stated that the NVRAM method would stop working with El Capitan's public release. Those typically need to install files into /usr/include and /usr/lib, which are also now restricted. I ran into a problem with the same root cause while trying to get pear/pecl modules and macports/homebrew apps installed. When you're done, it is highly recommended that you re-enable SIP by following the same steps, but using csrutil enable in step 3. Reboot and run the command that worked prior to El Capitan
With that mono is available: $ mono -version Since I use oh-my-zsh I defined MONO_HOME in ~/.zshrc and adjusted PATH accordingly: export MONO_HOME=/Library/Frameworks/amework/Home => installer: The install was successful. => installer: Package name is Mono Framework => Package installers may write to any location options such as -appdir are ignored.
=> Running installer for mono-mdk your password may be necessary. ➜ kafunk git:(master) brew cask install mono-mdk I first used brew cask to install Mono Framework and had to add /Library/Frameworks/amework/Home/bin to PATH environment variable. Mono JIT compiler version 4.6.2 (Stable 4.6.2.7/08fd525 Tue Nov 22 22:05:)Ĭopyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. $ brew cask uninstall mono-mdkĪnd installed it using brew install mono and removed all the configuration changes in ~/.zshrc. $ cat `which mcs`Įxport PATH=$PATH:/Library/Frameworks/amework/Versions/4.2.0/binĮxport PKG_CONFIG_PATH=/Library/Frameworks/amework/External/pkgconfig:/Library/Frameworks/amework/Versions/4.2.0/lib/pkgconfig:/Library/Frameworks/amework/Versions/4.2.0/share/pkgconfig:$PKG_CONFIG_PATHĮxec /Library/Frameworks/amework/Versions/4.2.0/bin/mono $MONO_OPTIONS /Library/Frameworks/amework/Versions/4.2.0/lib/mono/4.5/mcs.exe the first installation of Mono Framework using brew cask I found out that brew itself offers Mono (!) Mono JIT compiler version 4.2.0 (explicit/2701b19 Mon Aug 31 09:57:)Ĭopyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. In my case, I have 4.2.0 installed: $ which mono 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. 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
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.