From 877ae1077377c71a4c89f766531be8252cf5f3bf Mon Sep 17 00:00:00 2001
From: Joe Marcus Clarke
Starting with 2.16, GNOME now lives in + LOCALBASE instead of X11BASE. + This move can cause strange build problems if the proper + upgrade steps are not followed. However, if + after following all the steps, you may still see + errors like the following:
+ ++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 ++ +
This error indicates that an old libtool archive (a + file that ends with .la) is still lingering + about on your system. To find such files, search + through the system for libtool archive files that + contain the bad string + (/usr/X11R6/lib/libglade-2.0.la in the + example above). To do that, use the following + command:
+ ++# find / -type f -name "*.la" | xargs grep -l /usr/X11R6/lib/libglade-2.0.la ++ +
For each file that is found, use pkg_info + to determine which port or package installed it. + For example, if you find that + /usr/X11R6/lib/libgnomeui-2.0.la contains + the problem libtool reference, do the following:
+ ++# pkg_info -W /usr/X11R6/lib/libgnomeui-2.0.la ++ +
If you get back a package name, then force an + upgrade of that package using portupgrade. + 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 + /usr/X11R6/lib/libgnomeui-2.0.*. 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.