On 5/29/07, Ag. D. Hatzimanikas <[EMAIL PROTECTED]> wrote: > On Mon, May 28, at 11:08 Dan Nicholson wrote: > > On 5/28/07, Baho Utot <[EMAIL PROTECTED]> wrote: > > > When compiling libXfont-1.1.0.tar.bz2 part of Xorg Utilities > > > > > > I get the following > > > > > > checking for XFONT... configure: error: Package requirements (xproto > > > xtrans > > > fontsproto fontenc) were not met: > > > > > > No package 'xtrans' found > > > No package 'fontenc' found > > > > > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > > > installed software in a non-standard prefix. > > > > This very much sounds like PKG_CONFIG_PATH isn't set to the location > > that you're trying to install Xorg. Make sure that you have > > PKG_CONFIG_PATH=$XORG_PREFIX/lib/pkgconfig and you have that exported > > in the shell you're building in. > > Fisrt, I wanted to do that for a long time, and I did found the chance > with this post in support. > > I think we don't make it obvious, in any of our pages, how important > the PKG_CONFIG_PATH variable and a run for ldconfig (when you are > installing libs) is, for a succesfull build.
That's probably a good idea. I think this page would be the most appropriate place: http://www.linuxfromscratch.org/blfs/view/svn/introduction/important.html#unpacking I don't know what we'd title the sections, but the following two descriptions would be enough of a signal to me. pkg-config: Many packages make use of the pkg-config tool for determining if dependencies are installed and how they should be built with. It is important that the tool knows where to locate the .pc files for installed packages. Usually this would be in /usr/lib/pkgconfig, and the tool knows about that location by default. However, if you are installing packages to an alternate directory such as /opt/<package>, you will need to make sure that the environment variable is exported to contain the location /opt/<package>/lib/pkgconfig. See the pkg-config manpage for more details. ldconfig: The dynamic linker, /lib/ld-linux.so.2, uses a cache to store the names of the shared libraries used to speed up linking at runtime. If a package installs shared libraries, such as /usr/lib/lib<package>.so, it is important that you rebuild this cache since it may point to old libraries. This is accomplished by running the command ldconfig as root. Contents of the cache can be viewed with the command ldconfig -p. Suggestions? -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
