diff --git a/en/gnome/docs/faq2.sgml b/en/gnome/docs/faq2.sgml index 0d465feba2..522e96bc5c 100644 --- a/en/gnome/docs/faq2.sgml +++ b/en/gnome/docs/faq2.sgml @@ -1,6 +1,6 @@ - + %gnomeincludes; %includes; @@ -72,7 +72,7 @@ # make install clean -

For the best &gnomever; experience, you should install from +

For the best GNOME &gnomever; experience, you should install from ports, after adding the following macros to your /etc/make.conf file:

@@ -109,8 +109,25 @@ WITH_LAME= yes

The majority of GNOME &gnomever; compilation problems can be solved by making sure all the necessary GNOME &gnomever; components are - up-to-date. You may see a configure error - similar to the following:

+ up-to-date.

+ +

In general, when a GNOME &gnomever; component is not up-to-date, + you will see an error similar to the following:

+ + 
+checking for libgnomeui-2.0 libbonoboui-2.0 libbonobo-2.0 >= 2.2.1
+gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2 libglade-2.0... 
+configure: error: Library requirements (libgnomeui-2.0 libbonoboui-2.0
+libbonobo-2.0 >= 2.2.1 gnome-vfs-2.0 libgnomeprint-2.2 >= 2.3.0 libgnomeprintui-2.2
+libglade-2.0) not met; consider adjusting the PKG_CONFIG_PATH environment variable
+if your libraries are in a nonstandard prefix so pkg-config can find them.
+
+ +

Simply keeping your ports tree up-to-date will + prevent these errors.

+ +

If the pkg-config program is out-of-date, you may see + a configure error similar to the following:

 configure: error: *** pkg-config too old; version 0.14 or better required.