On 2019.06.19 14:10, Neil Bothwick wrote:
On Wed, 19 Jun 2019 20:45:03 +0800, Bill Kenworthy wrote:
> wifi ~ # unsymlink-lib --analyze
> /usr/lib needs to be a symlink to lib64!
> wifi ~ # ls -al /usr/lib
> lrwxrwxrwx 1 root root 10 Jan 4 13:37 /usr/lib -> /usr/lib64
> wifi ~ #
>
> The symlink looks the same as another unconverted system - so whats
the
> problem?
On this system, /usr/lib is a symlink to lib64, as the message states,
not /usr/lib64
% ls -ld /usr/lib
lrwxrwxrwx 1 root root 5 Jul 16 2015 /usr/lib -> lib64
--
Neil Bothwick
Ah, I think we've gotten to a bad splitting of hairs. /usr/lib ->
lib64 and /usr/lib -> /usr/lib64 have the same effect, but are not
quite the same. The first is a relative symlink, the second is
absolute, although both actually point to the same place.
Bill - you might try "rm /usr/lib" WITHOUT the trailing slash, to
remove the symlink. Then "ln -s lib64 /usr/lib" will recreate it in
the form unsymlink-lib seems to require.
Jack
