The default way to install a GNOME tarball needs the following 8 steps:
If some applications are still not able to respect newer aspects
of the gnome-include-filesystemhierarchy then you can
expand the environment variable CFLAGS by the command
«export CFLAGS="$CFLAGS -I/$INSTPREF/include/$MISSEDDIR
"»
and the environment variable CXXFLAGS by the command
«export CFLAGS="$CFLAGS -I/$INSTPREF/include/$MISSEDDIR
"»
(replace $INSTPREF by your installationpath). If you get any
fault-messages concerning missing header-files try to locate
the missed files and expand the corresponding CFLAGS-Variable
by the path to that file.
Note, calling «make install» normally includes the integration of debug info into the binaries. These infos naturally enlarge them. For erasing these infos and therefore for bulding applications and libraries being as small as possible you can (sometimes) call «make install-strip» instead of «make install».
If that possibility is not offered you may type «strip $INSTPATH/bin/$MADEBINS» and «strip -g $INSTPATH/bin/$MADELIBS » where $MADEBINS and MADELIBS denote those binaries and libraries just being made by you. BUT BE CARFULLY: don't forget «strip -g» while acting onto libraries. Otherwise they won't run any longer. [ Thanks to Volodymyr Babin who gave that hint]. One should know it and use it. I've just won more than 200 MB for my little old laptop.
If the compilation ends with «undefined reference to 'bind_textdomain_codeset'» then type «export LDFLAGS="-L/usr/local/gnu/lib -lintl"» before calling «./configure ... » (Replace «/usr/local/gnu/lib» by the path to the place where you find «libintl» in your system)
The installation procedure offers «configure» and «make» but doesn't understand «make install» or «--prefix=...»: After having typed «make» inside of the source-directory you will find there a directory «dist» containing a set of links pointing to the built libraries and applications. The next problem is, that the compiled tarball needs more than 450 mb although really you don't need more than 140 mb of libraries and applications. Execute the following commands as root for solving these problems:
Eric has recommended to add --enable-optimize=-O3 (flames > /dev/null) --disable-tests (!) --disable-logging --enable-strip-libs --enable-elf-dynstr-gc (not really neccesary) --enable-crypto (handy) --enable-cpp-exceptions (gcc can handle this) --disable-ldap (unless needed).
Important for GNOME2 installer: mozilla still requires glib-/gtk-config-files and libraries of GNOME 1.4 although mozilla itself is required by nautilus. Therefore you should now install the first basic libraries of GNOME 1.4 in that manner which has been described in the section How Can I Use The Well Known GNOME-1.x Applications In The GNOME-2 Desktop System?
If you install this library under GNOME it won't be found by the python-interpreter. Therefore the exception underlines the rule: This tarball must be installed wherever your python has been installed!
Note: Although the python-gtk- and gnome-python-bindings for GNOME-2 already exist they should not be installed (for the moment):
Note: galeon tests the file «/usr/local/mozilla/dist/lib/defaults/pref/all.js»
but even still in mozilla 0.9.4 it is offered under
«/usr/local/mozilla/dist/bin/defaults/pref/all.js»
For solving that problem do this
1) cd /usr/local/mozilla/dist/lib/
2) ln -s ../bin/defaults defaults.
Then use
«
./configure --prefix=/opt/gnome
--with-mozilla-libs=/usr/local/mozilla/dist/lib
--with-mozilla-includes=/usr/local/mozilla/dist/include
»
The tarball of galeon 0.12.4 contains a specialization which doesn't respect at least my environment: In the file «src/mozilla/TOCProtocolHandler.cpp» there is included a file «g++-3/string» if the gcc-compiler has version > 2.90 or > 2.95 otherwise the file «string». But my gcc version 2.95.2 stores its cpp headers still under /usr/lib. Therefore at least I have had to replace the strings «g++-3/string» by the string «string».
© Karsten Reincke, Osnabrück (Germany) 2000/2001/2002.