more on GIMP (et al) configure problems.

Mon Apr  6 18:48:49 BST 1998 Tony Gale  <gale@gtk.org>

        * docs/gtkfaq.sgml: more on GIMP (et al) configure
          problems.

2 files changed, 62 insertions, 10 deletions

diff --git a/docs/faq/gtkfaq.sgml b/docs/faq/gtkfaq.sgml
index 2e16cc3f4d..1e9257d2c7 100644
--- a/docs/faq/gtkfaq.sgml
+++ b/docs/faq/gtkfaq.sgml
@@ -8,7 +8,7 @@
 
 <!-- NOTE: Use only one author tag, otherwise sgml2txt barfs - TRG --> 
 <author>Nathan Froyd, Tony Gale, Shawn T. Amundson.
-<date>April 2nd 1998
+<date>April 6nd 1998
 <abstract>
 This document is intended to answer questions that are likely to be 
 frequently asked by programmers using GTK+ or people who are just
@@ -210,14 +210,30 @@ found or are the wrong version. Generally, the compiler will complain about an
 'unresolved symbol'.  There are two things you need to check:
 <itemize>
 <item>Make sure that the libraries can be found. You want to edit 
-/etc/ld.so.conf to include /usr/local/lib (or whereever you installed GTK+),
+/etc/ld.so.conf to include the directories which contain the GTK libraries,
  so it looks something like:
 <verb>
 /usr/X11R6/lib
 /usr/local/lib
 </verb>
-Then you need to run /sbin/ldconfig as root. 
-<p>
+Then you need to run /sbin/ldconfig as root. You can find what directory
+GTK is in using
+<verb>
+gtk-config --libs
+</verb>
+
+If your system doesn't use ld.so to find libraries (such as Solaris), then
+you will have to use the LD_LIBRARY_PATH environment variable (or compile
+the path into your program, which I'm not going to cover here). So, with a
+Bourne type shell you can do (if your GTK libraries are in /usr/local/lib):
+<verb>
+export LD_LIBRARY_PATH=/usr/local/lib
+</verb>
+and in a csh, you can do:
+<verb>
+setenv LD_LIBRARY_PATH /usr/local/lib
+</verb>
+
 <item>Make sure the linker is finding the correct set of libraries. If you
 have a Linux distribution that installs GTK+ (e.g. RedHat 5.0) then this 
 older version may be used. Now (assuming you have a RedHat
@@ -236,7 +252,7 @@ and reinstall gtk+.
 <!-- ----------------------------------------------------------------- -->
 <sect1>When installing The GIMP, configure reports that it can't find GTK.
 <p>
-There are two common reasons for this:
+There are several common reasons for this:
 <itemize>
 <item>You have an old version of GTK installed somewhere. RedHat 5.0, for 
 example, installs an older copy of GTK that will not work with the latest 
@@ -252,7 +268,17 @@ to check for both of these. This should return a value of at least 0.99.8
 for things to work properly with GIMP 0.99.23. If it returns a value
 different from what you expect, then you have an old version of GTK on
 your system.
+<P>
+<item>The ./configure script can't find the GTK libraries. As ./configure
+compiles various test programs, it needs to be able to find the GTK
+libraries. See the question above for help on this.
 </itemize>
+<p>
+If none of the above help, then have a look in config.log, which is
+generated by ./configure as it runs. At the bottom will be the last
+action it took before failing. If it is a section of source code, copy
+the source code to a file and compile it with the line just above it in
+config.log. If the compilation is successful, try executing it.
 
 <!-- ***************************************************************** -->
 <sect>Development of GTK+
diff --git a/docs/gtkfaq.sgml b/docs/gtkfaq.sgml
index 2e16cc3f4d..1e9257d2c7 100644
--- a/docs/gtkfaq.sgml
+++ b/docs/gtkfaq.sgml
@@ -8,7 +8,7 @@
 
 <!-- NOTE: Use only one author tag, otherwise sgml2txt barfs - TRG --> 
 <author>Nathan Froyd, Tony Gale, Shawn T. Amundson.
-<date>April 2nd 1998
+<date>April 6nd 1998
 <abstract>
 This document is intended to answer questions that are likely to be 
 frequently asked by programmers using GTK+ or people who are just
@@ -210,14 +210,30 @@ found or are the wrong version. Generally, the compiler will complain about an
 'unresolved symbol'.  There are two things you need to check:
 <itemize>
 <item>Make sure that the libraries can be found. You want to edit 
-/etc/ld.so.conf to include /usr/local/lib (or whereever you installed GTK+),
+/etc/ld.so.conf to include the directories which contain the GTK libraries,
  so it looks something like:
 <verb>
 /usr/X11R6/lib
 /usr/local/lib
 </verb>
-Then you need to run /sbin/ldconfig as root. 
-<p>
+Then you need to run /sbin/ldconfig as root. You can find what directory
+GTK is in using
+<verb>
+gtk-config --libs
+</verb>
+
+If your system doesn't use ld.so to find libraries (such as Solaris), then
+you will have to use the LD_LIBRARY_PATH environment variable (or compile
+the path into your program, which I'm not going to cover here). So, with a
+Bourne type shell you can do (if your GTK libraries are in /usr/local/lib):
+<verb>
+export LD_LIBRARY_PATH=/usr/local/lib
+</verb>
+and in a csh, you can do:
+<verb>
+setenv LD_LIBRARY_PATH /usr/local/lib
+</verb>
+
 <item>Make sure the linker is finding the correct set of libraries. If you
 have a Linux distribution that installs GTK+ (e.g. RedHat 5.0) then this 
 older version may be used. Now (assuming you have a RedHat
@@ -236,7 +252,7 @@ and reinstall gtk+.
 <!-- ----------------------------------------------------------------- -->
 <sect1>When installing The GIMP, configure reports that it can't find GTK.
 <p>
-There are two common reasons for this:
+There are several common reasons for this:
 <itemize>
 <item>You have an old version of GTK installed somewhere. RedHat 5.0, for 
 example, installs an older copy of GTK that will not work with the latest 
@@ -252,7 +268,17 @@ to check for both of these. This should return a value of at least 0.99.8
 for things to work properly with GIMP 0.99.23. If it returns a value
 different from what you expect, then you have an old version of GTK on
 your system.
+<P>
+<item>The ./configure script can't find the GTK libraries. As ./configure
+compiles various test programs, it needs to be able to find the GTK
+libraries. See the question above for help on this.
 </itemize>
+<p>
+If none of the above help, then have a look in config.log, which is
+generated by ./configure as it runs. At the bottom will be the last
+action it took before failing. If it is a section of source code, copy
+the source code to a file and compile it with the line just above it in
+config.log. If the compilation is successful, try executing it.
 
 <!-- ***************************************************************** -->
 <sect>Development of GTK+