Dan Nicholson wrote:
> On 5/29/07, Ag. D. Hatzimanikas <[EMAIL PROTECTED]> wrote:

>> 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

That seems like the most appropriat place.

> I don't know what we'd title the sections, but the following two
> descriptions would be enough of a signal to me.

After "Dependencies"

<title>Package Dependency Self Checking</title>

> pkg-config:
> Many packages make use of the <xref linkend='pkgconfig'/> tool for 
> determining if
> dependencies are installed and how they should be built with. It is

s/with//

> 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.

<title>Library Linking Issues</title>

> 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

s/the//

> a package installs shared libraries, such as /usr/lib/lib<package>.so,
> it is important that this cache be rebuilt since it may point to old
> libraries. 

In many cases, this will be done during the 'make install' command of
the package, but in some cases it is not.

This is manually accomplished by running the command ldconfig as
> root. Contents of the cache can be viewed with the command `ldconfig -p`.

  -- Bruce
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to