#859 closed defect (fixed)
gpm specific ldconfig command unnecessary
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | BOOK | Version: | ~CVS |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
On the gpm page, there is an ldconfig command that is run to link in gpm's new library, with explanatory text that says "during installation, gpm says to run this command".
In fact, during installation, the standard text that is displayed when nearly any library is installed via libtool is shown, that says the simple solution is to just run "ldconfig", with no special parameters. In fact, that's what every other package in BLFS does, and it's really the better way to go, as the command does not need to be kept up to date when the package changes.
My suggestion is to just change it to be like all the other packages: run ldconfig with no parameters.
Change History (3)
comment:1 by , 21 years ago
| Status: | new → assigned |
|---|
comment:2 by , 21 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Changed the ldconfig command
Note:
See TracTickets
for help on using tickets.
Confirmed the report. Here's output from 'make install':
WARNING: We installed a lib, you should now call ldconfig f.i.: ldconfig -n -l /home/rml/gpmstuff/lib/libgpm.so.1.19.0 Or to update everything just type ldconfig