We recommend that each time you compile GDAM, you use a fresh copy of the source code. The reason for this is that many configuration options are stored in files such as config.cache and it is therefore possible that the makefiles don't match your current system configuration. (This can happen if you install a package after running configure). Check out a new copy from cvs, or re-unzip the tarball or (faster) delete the config.cache.
We use GNU automake for building our programs. This means that once you have the tarball, the following standard procedure should apply:
% ./configure % make % make install |
If you have the cvs version, run ./autogen.sh instead of ./configure. This will install gdam in /usr/local/lib/gdam/, /usr/local/bin/gdam*. If you specify the option --prefix=/usr to ./configure it will install in /usr instead.
The version of gcc most commonly distributed with FreeBSD, 2.95.2 19991024, will not compile GDAM. To work around this, upgrade to egcc. If you have not already done so, install ports by running /stand/sysinstall. Then move to /ports/lang/gcc-devel/ and make install.
When configuring GDAM, you need to specify the proper path to the gtk-config command, and to use egcc. Your command will probably be:
% GTK_CONFIG=/usr/X11R6/bin/gtk12-config CC=egcc ./configure |
Now, use gmake to build:
% gmake; gmake install |
In order for your system to know were the libs are installed, you might need to do the following:
% ldconfig |
If you still get errors about missing libraries running gdam:
Make sure that /etc/ld.so.conf contains the relevant /usr/*/lib directory.
Alternately, to use GDAM without installing it, set the LD_LIBRARY_PATH environment variable to include the directory where the libraries reside. You should modify your shell startup script or /etc/profile if you are going to run gdam frequently.