diff --git a/ChangeLog b/ChangeLog index 74f28fd0e2..22c64b7911 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +Mon Apr 6 18:48:49 BST 1998 Tony Gale + + * docs/gtkfaq.sgml: more on GIMP (et al) configure + problems. + Mon Apr 6 08:05:23 1998 Owen Taylor * gtk/gtkbutton.c (gtk_button_paint): Take border in diff --git a/ChangeLog.pre-2-0 b/ChangeLog.pre-2-0 index 74f28fd0e2..22c64b7911 100644 --- a/ChangeLog.pre-2-0 +++ b/ChangeLog.pre-2-0 @@ -1,3 +1,8 @@ +Mon Apr 6 18:48:49 BST 1998 Tony Gale + + * docs/gtkfaq.sgml: more on GIMP (et al) configure + problems. + Mon Apr 6 08:05:23 1998 Owen Taylor * gtk/gtkbutton.c (gtk_button_paint): Take border in diff --git a/ChangeLog.pre-2-10 b/ChangeLog.pre-2-10 index 74f28fd0e2..22c64b7911 100644 --- a/ChangeLog.pre-2-10 +++ b/ChangeLog.pre-2-10 @@ -1,3 +1,8 @@ +Mon Apr 6 18:48:49 BST 1998 Tony Gale + + * docs/gtkfaq.sgml: more on GIMP (et al) configure + problems. + Mon Apr 6 08:05:23 1998 Owen Taylor * gtk/gtkbutton.c (gtk_button_paint): Take border in diff --git a/ChangeLog.pre-2-2 b/ChangeLog.pre-2-2 index 74f28fd0e2..22c64b7911 100644 --- a/ChangeLog.pre-2-2 +++ b/ChangeLog.pre-2-2 @@ -1,3 +1,8 @@ +Mon Apr 6 18:48:49 BST 1998 Tony Gale + + * docs/gtkfaq.sgml: more on GIMP (et al) configure + problems. + Mon Apr 6 08:05:23 1998 Owen Taylor * gtk/gtkbutton.c (gtk_button_paint): Take border in diff --git a/ChangeLog.pre-2-4 b/ChangeLog.pre-2-4 index 74f28fd0e2..22c64b7911 100644 --- a/ChangeLog.pre-2-4 +++ b/ChangeLog.pre-2-4 @@ -1,3 +1,8 @@ +Mon Apr 6 18:48:49 BST 1998 Tony Gale + + * docs/gtkfaq.sgml: more on GIMP (et al) configure + problems. + Mon Apr 6 08:05:23 1998 Owen Taylor * gtk/gtkbutton.c (gtk_button_paint): Take border in diff --git a/ChangeLog.pre-2-6 b/ChangeLog.pre-2-6 index 74f28fd0e2..22c64b7911 100644 --- a/ChangeLog.pre-2-6 +++ b/ChangeLog.pre-2-6 @@ -1,3 +1,8 @@ +Mon Apr 6 18:48:49 BST 1998 Tony Gale + + * docs/gtkfaq.sgml: more on GIMP (et al) configure + problems. + Mon Apr 6 08:05:23 1998 Owen Taylor * gtk/gtkbutton.c (gtk_button_paint): Take border in diff --git a/ChangeLog.pre-2-8 b/ChangeLog.pre-2-8 index 74f28fd0e2..22c64b7911 100644 --- a/ChangeLog.pre-2-8 +++ b/ChangeLog.pre-2-8 @@ -1,3 +1,8 @@ +Mon Apr 6 18:48:49 BST 1998 Tony Gale + + * docs/gtkfaq.sgml: more on GIMP (et al) configure + problems. + Mon Apr 6 08:05:23 1998 Owen Taylor * gtk/gtkbutton.c (gtk_button_paint): Take border in 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 @@ Nathan Froyd, Tony Gale, Shawn T. Amundson. -April 2nd 1998 +April 6nd 1998 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: 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: /usr/X11R6/lib /usr/local/lib -Then you need to run /sbin/ldconfig as root. -

+Then you need to run /sbin/ldconfig as root. You can find what directory +GTK is in using + +gtk-config --libs + + +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): + +export LD_LIBRARY_PATH=/usr/local/lib + +and in a csh, you can do: + +setenv LD_LIBRARY_PATH /usr/local/lib + + 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+. When installing The GIMP, configure reports that it can't find GTK.

-There are two common reasons for this: +There are several common reasons for this: 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. +

+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. +

+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. 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 @@ Nathan Froyd, Tony Gale, Shawn T. Amundson. -April 2nd 1998 +April 6nd 1998 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: 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: /usr/X11R6/lib /usr/local/lib -Then you need to run /sbin/ldconfig as root. -

+Then you need to run /sbin/ldconfig as root. You can find what directory +GTK is in using + +gtk-config --libs + + +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): + +export LD_LIBRARY_PATH=/usr/local/lib + +and in a csh, you can do: + +setenv LD_LIBRARY_PATH /usr/local/lib + + 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+. When installing The GIMP, configure reports that it can't find GTK.

-There are two common reasons for this: +There are several common reasons for this: 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. +

+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. +

+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. Development of GTK+