Talk:Mac OSX Installation
Just a few comments:
- point 2) dependencies: I am not sure why it seems so hard to install all the necessary packages? Does fink not deal properly with dependencies?
- point 3) "the packaged versions available on the web do not work": why not? is it because the "configure" script needs to be regenerated specifically for Mac OSX?
- point 7) this should not be necessary since "pkg-config" should be able to find GTS using the PKG_CONFIG_PATH defined in point 5)
--Popinet 14:38, 8 November 2007 (PST)
- We did an installation yesterday on Luc Deike's system but I am not sure what the state of the system was before I started helping. However I do know that X11 was not installed properly (I added an instruction on the page). Perhaps pkgconfig was not properly installed, which is why we needed gts-config. On my own system I did not need all the additional packages, but they were probably installed before. Every single time I did a Mac OSX installation I had to do some trial and error on the list of packages. It is not a problem with the dependencies, but that when you start the installation you do not know what is installed or not. This answers your questions about point 2) and 7). As for point 3), I have not tried the packaged versions, somebody should check them. --Zaleski 03:56, 9 November 2007 (PST)
As of August 2010 I was having trouble making fink work on my new Snow Leopard MacOSX 10.6 Intel X86_64 so I switched to MacPorts. (When you do this you should uninstall fink by removing the /sw directory otherwise the two will interfere with each other.) Everybody else was telling me that MacPorts was better anyway, as is reflected in the article. Then I had trouble configuring gts-mainline until I realized that one had specify the ACLOCAL path like:
export ACLOCAL_FLAGS="-I/opt/local/share/aclocal $ACLOCAL_FLAGS"
There is in fact a whole lot of environment variables that should be set to use with MacPorts to path starting with /opt/local but this one was pretty obscure ...
The packages that must be installed under MacPorts are different from those listed. They are installed by
sudo port install pkgconfig glib2 glib2-devel gtkglext startup-notification
If you get an error like
libtool: Version mismatch error. This is libtool 2.2.4, but the libtool: definition of this LT_INIT comes from an older release. libtool: You should recreate aclocal.m4 with macros from libtool 2.2.4 libtool: and run autoconf again.
uninstall the libtool port:
sudo port uninstall libtool
and rerun the installation starting with
sh autogen.sh --prefix=/opt/gerris
This should take you through gerris installation.
gtk and gtkgl issues
There is more trouble with gfsview. As Arnaud wrote, the gtkglext packaged in MacPorts won't work. I uninstalled the MacPorts gtkglext (but see below), downloaded it from http://projects.gnome.org/gtkglext/download.html and re-installed gtkglext with
tar xfz gtkglext-1.0.6.tar.gz cd gtkglext-1.0.6 export LDFLAGS=-L/usr/X11R6/lib ./configure --with-gl-includedir=/usr/X11R6/include/ --with-gl-libdir=/usr/X11R6/lib make sudo make install
(Apparently gtkglext has to be told by the LDFLAGS environment variable where to find the X11 libraries... LD_LIBRARY_PATH won't work.) But I still had an error like:
% gfsview2D Xlib: extension "RANDR" missing on display ":0.0". dyld: lazy symbol binding failed: Symbol not found: _GTK_WIDGET_NO_WINDOW Referenced from: /opt/local/lib/libgtkglext-x11-1.0.0.dylib Expected in: flat namespace dyld: Symbol not found: _GTK_WIDGET_NO_WINDOW Referenced from: /opt/local/lib/libgtkglext-x11-1.0.0.dylib Expected in: flat namespace Trace/BPT trap
This is apparently due to an incompatibility between gtkglext and gtk-2.20. gtk-2.20 is the version installed currently by MacPorts. So I had to downgrade gtk by installing an older version of gtk+- from source. I donwloaded 2.19.7 from http://ftp.gnome.org/pub/gnome/sources/gtk+ then
tar xvfj gtk+-2.19.7.tar.bz2 cd gtk+-2.19.7 ./configure --without-libtiff --without-libjpeg sudo make sudo make install
Perhaps with the downgraded gtk , gtkglext from macports would work after all but I did not check.