Opened 14 years ago

Closed 14 years ago

#2457 closed task (fixed)

BLFS doesn't document the library search process

Reported by: alexander@… Owned by: blfs-book@…
Priority: normal Milestone: 6.3
Component: BOOK Version: SVN
Severity: normal Keywords:
Cc:

Description

BLFS has the following boilerplate for library configuration:

As with most libraries, there is no configuration to do, save that the library directory, i.e., /opt/lib or /usr/local/lib should appear in /etc/ld.so.conf so that ldd can find the shared libraries. After checking that this is the case, /sbin/ldconfig should be run while logged in as root.

However, this is very insufficient, because it only ensures that the library can be found at runtime. Nothing (e.g., setting PATH so that it includes foo-config, adjusting pkgconfig path, or, in the worst case, setting LDFLAGS) is done to ensure that the packages that need the library can find it at the build time.

Change History (4)

comment:1 by tushar@…, 14 years ago

If someone is installing outside /usr, http://www.linuxfromscratch.org/blfs/view/svn/introduction/beyond.html provides information on how to account for the non-standard installation. Though, the setting of LDFLAGS is missing. I have added that. If that is sufficient, please close this ticket.

comment:2 by alexander@…, 14 years ago

The following remains:

  • the boilerplate doesn't reference the "Going Beyond BLFS" page, and
  • it is misnamed, because its content about paths and flags applies to packages in BLFS, too.

comment:3 by tushar@…, 14 years ago

The title Beyond BLFS is correct. It indicates going beyond BLFS, not just in terms of installing a new package but also installing a package in a "non-standard" way.

comment:4 by Randy McMurchy, 14 years ago

Resolution: fixed
Status: newclosed

I'm not sure that the issue being raised really should have to do with the "boilerplate" message at all. That message simply lets the users know what to do to ensure the library is found at run-time.

Mention of how to configure the system to find libraries at build-time is discussion for a page other than individual packages.

I'm going to close this ticket, and if it is determined that information on how to make libraries available at build-time is needed for the book, let's open a new ticket with some information on exactly where the information belongs.

If I'm wrong about all this, feel free to reopen this ticket.

Note: See TracTickets for help on using tickets.