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

Add some instructions about what to do if you encounter an error like:

Browse source 
grep: /usr/X11R6/lib/libglade-2.0.la: No such file or directory
sed: /usr/X11R6/lib/libglade-2.0.la: No such file or directory
libtool: link: `/usr/X11R6/lib/libglade-2.0.la' is not a valid libtool archive

These are becoming more and more prevalent now that GNOME has been moved
to LOCALBASE.
This commit is contained in:
Joe Marcus Clarke 2006-11-03 21:14:11 +00:00
parent 1fd366d976
commit 877ae10773
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=28998
1 changed files with 51 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.115 2006/10/28 21:50:26 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.116 2006/10/29 20:46:32 marcus Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME &gnomever; FAQ">
<!ENTITY % navinclude.gnome "INCLUDE">
]>
@ -201,6 +201,56 @@ options _KPOSIX_PRIORITY_SCHEDULING
rebuild of all GNOME-related apps (and a fair number of other apps) without
retaining old versions of libraries in <tt>/usr/local/lib/compat/pkg</tt>.
</p>
<p>Starting with 2.16, GNOME now lives in
<tt>LOCALBASE</tt> instead of <tt>X11BASE</tt>.
This move can cause strange build problems if <a
href="&base;/gnome/docs/faq216.html">the proper
upgrade steps</a> are not followed. However, if
after following all the steps, you may still see
errors like the following:</p>
<pre>
grep: /usr/X11R6/lib/libglade-2.0.la: No such file or directory
sed: /usr/X11R6/lib/libglade-2.0.la: No such file or directory
libtool: link: `/usr/X11R6/lib/libglade-2.0.la' is not a valid libtool archive
</pre>
<p>This error indicates that an old libtool archive (a
file that ends with <tt>.la</tt>) is still lingering
about on your system. To find such files, search
through the system for libtool archive files that
contain the bad string
(<tt>/usr/X11R6/lib/libglade-2.0.la</tt> in the
example above). To do that, use the following
command:</p>
<pre>
# find / -type f -name "*.la" | xargs grep -l /usr/X11R6/lib/libglade-2.0.la
</pre>
<p>For each file that is found, use <tt>pkg_info</tt>
to determine which port or package installed it.
For example, if you find that
<tt>/usr/X11R6/lib/libgnomeui-2.0.la</tt> contains
the problem libtool reference, do the following:</p>
<pre>
# pkg_info -W /usr/X11R6/lib/libgnomeui-2.0.la
</pre>
<p>If you get back a package name, then force an
upgrade of that package using <tt>portupgrade</tt>.
If you do not get back anything, then you can safely
delete the libtool archive file. Once the file is
gone, check the directory from which you deleted it
for other files with similar names. In the example
above, check for
<tt>/usr/X11R6/lib/libgnomeui-2.0.*</tt>. If you
find any matching files, delete those, too. Once
all of the files are gone, you can resume building
your original port. Repeat these steps if you
encounter further such problems.</p>
</li>
<!-- Q3 -->