Opened 22 years ago
Closed 22 years ago
#474 closed defect (fixed)
libcurses.a symlink command no longer needed + redo .so symlinks?
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | highest | Milestone: | |
Component: | Book | Version: | CVS |
Severity: | normal | Keywords: | |
Cc: |
Description
ncurses 5.3 now creates the libcurses.a symlink on its' own so the command in the book which creates the symlink is no longer required.
Change History (7)
comment:1 by , 22 years ago
comment:2 by , 22 years ago
The libncurses.so symlink created by the ncurses package points to libncurses.so.5, while the libcurses.so symlink actually points to libncurses.so.5.3 instead. In the book we point libcurses.so at libncurses.so.5, change this to point to .5.3
comment:3 by , 22 years ago
Priority: | high → highest |
---|
comment:4 by , 22 years ago
This is from bug #476 which I'm marking a duplicate of this bug. It seems the previous comment is exactly like the following one, but just to be one the safe side here it is anyways.
when the ncurses 5.3 packages installes the libcurses.so symlink it points the link to libncurses.so.5.3 instead of libncurses.so.5 which is what we change it to in the book.
I propose that we change the instructions so that when we redo the libcurses.so symlink to make it point to the prper directory, it also points to libncurses.so.5.3, since that seems to have been the intent of the package maintainer.
http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2003/01/0589.html
comment:6 by , 22 years ago
Summary: | libcurses.a symlink command no longer needed → libcurses.a symlink command no longer needed + redo .so symlinks? |
---|
comment:7 by , 22 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
http://archive.linuxfromscratch.org/mail-archives/lfs-dev/2003/01/0585.html