os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Give an example of the error you get when your bidness isn't

Browse source 
up-to-date.
This commit is contained in:
Adam Weinberger 2003-10-17 15:43:25 +00:00
parent f05c6b8258
commit a3879e283d
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=18464
1 changed files with 21 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
en/gnome/docs/faq2.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.48 2003/10/10 07:24:36 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.49 2003/10/17 15:34:50 adamw Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME &gnomever; FAQ">
<!ENTITY % gnomeincludes SYSTEM "../includes.sgml"> %gnomeincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -72,7 +72,7 @@
# make install clean
</pre>
<p>For the best &gnomever; experience, you should install from
<p>For the best GNOME &gnomever; experience, you should install from
ports, after adding the following macros to your
<tt>/etc/make.conf</tt> file:</p>
@ -109,8 +109,25 @@ WITH_LAME= yes
<!-- A2 -->
<p>The majority of GNOME &gnomever; compilation problems can be solved
by making sure all the necessary GNOME &gnomever; components are
<a href="#q6">up-to-date</a>. You may see a configure error
similar to the following:</p>
<a href="#q6">up-to-date</a>.</p>
<p>In general, when a GNOME &gnomever; component is not up-to-date,
you will see an error similar to the following:</p>
<pre>
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.
</pre>
<p>Simply keeping your ports tree <a href="#q6">up-to-date</a> will
prevent these errors.</p>
<p>If the <tt>pkg-config</tt> program is out-of-date, you may see
a configure error similar to the following:</p>
<pre>
configure: error: *** pkg-config too old; version 0.14 or better required.