This is simply a # convenience for users and should only be done on systems where # all Ferret users work under the same shell (such as tcsh or bash). # desired ferret_paths location -> /usr/local # To duplicate behavior found in older version of Ferret, you can # create a link (shortcut) 'ferret_paths' that refers to either # 'ferret_paths.csh' or 'ferret_paths.sh'. # FER_DSETS -> /Users/jourdain/Ferret-7.4.4/fer_dsets # Enter the name of the directory where you want to place # the newly created 'ferret_paths.csh' and 'ferret_path.sh' # files for example, '/usr/local'. # FER_DIR -> /Users/jourdain/Ferret-7.4.4 # Enter the name of the directory where the 'fer_' # file was installed/extracted (FER_DSETS). The location recommended # in the Ferret installation guide was '/usr/local/ferret'. # Enter the name of the directory where the 'fer_' # file was installed/extracted (FER_DIR).
To resolve this either rebuild the dependency to be a universal binary or build a mono that matches your dependencies.# Enter your choice: # (1) Install executables, (2) Customize ferret_paths files, (3,q,x) Exit # (1, 2, 3, q, x) -> 2 # Customize ferret_paths files. This means that configure was able to resolve some optional dependencies in your environment (gettext or glib primarily) that have been compiled for 64-bit when you are building a 32-bit mono or vice-versa. If you receive an error like: ld: warning: in /usr/local/lib/libiconv.dylib, file was built for unsupported file format which is not the architecture being linked (i386) configure -prefix=$PREFIX & make & make install) done # Ensure you have write permissions to /usr/localįor i in */configure do (cd `dirname $i`. If you just want to install Mono without thinking too much, just copy and paste the following script, and enter your root password when requested: PREFIX=/usr/local
To build Mono in 32 bit mode instead use this to configure the build: CFLAGS="-m32 -arch i386" LDFLAGS="-m32 -arch i386". autogen.sh -prefix=$PREFIX -disable-nls Once you do this, run the following commands, remember to replace PREFIX with your installation prefix that you selected: PATH=$PREFIX/bin:$PATH To build Mono from a Git Source Code checkout, you will want to have the official Mono installed on the system, as the build requires a working C# compiler to run. Building Mono From a Git Source Code Checkout configure -prefix=$PREFIX -disable-nlsīy the end of this process, you will have Mono installed on your PREFIX directory.
If you wish to compile Mono in 64 bit mode instead use this to configure the build. configure -prefix=$PREFIX -disable-nls -build=i386-apple-darwin11.2.0 Once you have your dependencies installed all you need to do is run the following command where VERSION is the package version number and PREFIX is your installation prefix: PREFIX=/usr/local through Homebrew brew install autoconf automake libtool pkg-config cmake python3 You need to install those in your path, e.g. Mono uses GNU autoconf, automake and libtool. On Mavericks and later versions you will need to install some tools that are no longer part of the developer SDK, but luckily this is a very simple process. Building Monoīuilding Mono is a very simple process as Mono has very few external dependencies. It is strongly advised not to install Mono from source in /usr as it might conflict with Mono as installed by the Mono package.
If you have more than one Mono installation (for example to keep multiple versions around), you will want to read the document on Parallel Mono Environments on how to keep your various Mono installations separate. For example, I like to use the directory /opt/mono, so I would replace PREFIX with /opt/mono in the following discussion. Your Mono installation and its dependencies will be installed there. Pick an installation directory where you want your new copy of Mono to be installed.