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