vim won't start on new installation.

trujillo-gc · 2023-08-29 18:59:49

Hi all, Again a newbie question:
I have installed vim in a fresh installation and it does not find dependencies.

When I install vim I get this dependencies message,

[at@arch ~]$ sudo pacman -S vim
resolving dependencies...
looking for conflicting packages...

Packages (2) vim-runtime-9.0.1678-1.0  vim-9.0.1678-1.0

Total Installed Size:  40.06 MiB

:: Proceed with installation? [Y/n] y
(2/2) checking keys in keyring                               [################################] 100%
(2/2) checking package integrity                             [################################] 100%
(2/2) loading package files                                  [################################] 100%
(2/2) checking for file conflicts                            [################################] 100%
(2/2) checking available disk space                          [################################] 100%
:: Processing package changes...
(1/2) installing vim-runtime                                 [################################] 100%
Optional dependencies for vim-runtime
    sh: support for some tools and macros [installed]
    python: demoserver example tool [installed]
    gawk: mve tools upport [installed]
(2/2) installing vim                                         [################################] 100%
Optional dependencies for vim
    python: Python language support [installed]
    ruby: Ruby language support
    lua: Lua language support
    tcl: Tcl language support
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating icon theme caches...
(3/3) Updating the desktop file MIME type cache...

And this is the error when I try to open vim,

[at@arch ~]$ vim
vim: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory

Please, what should I do to fix it?

Thank, Alberto

abaumann · 2023-09-07 06:04:07

Now that python and pax-utils is broken:

Traceback (most recent call last):
File "/usr/bin/lddtree", line 60, in <module>
from elftools.common import exceptions
ModuleNotFoundError: No module named 'elftools'

ldd says:

ldd /usr/bin/vim
linux-gate.so.1 (0xf7ef3000)
libm.so.6 => /usr/lib/libm.so.6 (0xf7911000)
libncursesw.so.6 => /usr/lib/libncursesw.so.6 (0xf789c000)
libacl.so.1 => /usr/lib/libacl.so.1 (0xf7893000)
libgpm.so.2 => /usr/lib/libgpm.so.2 (0xf788a000)
libperl.so => not found
libc.so.6 => /usr/lib/libc.so.6 (0xf766b000)
/lib/ld-linux.so.2 => /usr/lib/ld-linux.so.2 (0xf7ef5000)

So rebuilding vim should be enough. Again. Why perl has been pushed to stable is not clear to me.

abaumann · 2023-09-07 06:05:24

reschedule-for-rebuild vim > ~/x; source ~/x
vim 5a5209b486a0cc0db182a19d49bd82ac4d8960fb 0000000000000000000000000000000000000000 5467c931634c751e3e1debf5fa62f04284247ef7 extra
vim c28f552426d5762bfac58e9b583cc1c12471ea90 0000000000000000000000000000000000000000 5467c931634c751e3e1debf5fa62f04284247ef7 extra
vim ce0feb9d43bbc512830f9d1e73b2adcd5b36af97 0000000000000000000000000000000000000000 5467c931634c751e3e1debf5fa62f04284247ef7 extra
vim ce833f400f67b1aeea151227ecd0c18072a5cc46 0000000000000000000000000000000000000000 5467c931634c751e3e1debf5fa62f04284247ef7 extra
92

Four upstream versions? This also doesn't sound right.
At the end the script says '92', so I guess, it was able to schedule a rebuild.

abaumann · 2023-09-07 09:54:21

Rebuilding didn't change anything. Weird, 64-bit vim doesn't require a libperl.so?

abaumann · 2023-09-07 09:58:10

Again, I'm puzzled by what PKGBUILD we are actually using to build packages: I see an optdepends=perl for gvim, but
nowhere a depends=perl.

It could be an automatically detected dependency on libperl.so, but this should be on 'gvim' and not on 'vim'.

Nevertheless, if I install perl, it still doesn't find libperl.so.

A workaround for running vim was:

cat > /etc/ld.so.conf.d/perl.conf <<EOF
/usr/lib/perl5/5.36/core_perl/CORE
EOF

(this feels wrong though it works)

abaumann · 2023-09-07 10:05:15

aha, vim uses perl 5.38 (stable still has perl 5.36):

Dynamic section at offset 0x4b7720 contains 33 entries:
Tag Type Name/Value
0x00000001 (NEEDED) Shared library: [libm.so.6]
0x00000001 (NEEDED) Shared library: [libncursesw.so.6]
0x00000001 (NEEDED) Shared library: [libacl.so.1]
0x00000001 (NEEDED) Shared library: [libgpm.so.2]
0x00000001 (NEEDED) Shared library: [libperl.so]
0x00000001 (NEEDED) Shared library: [libc.so.6]
0x0000001d (RUNPATH) Library runpath: [/usr/lib/perl5/5.38/core_perl/CORE]

So, know I would have to push perl 5.38 to stable (which I will not do because it potentially breaks a lot of things).

abaumann · 2023-09-07 10:09:19

It's vital to remove this ldconfig config file once perl 5.38 is in stable!

Arch Linux

#1 2023-08-29 18:59:49

vim won't start on new installation.

#2 2023-09-07 06:04:07

Re: vim won't start on new installation.

#3 2023-09-07 06:05:24

Re: vim won't start on new installation.

#4 2023-09-07 09:54:21

Re: vim won't start on new installation.

#5 2023-09-07 09:58:10

Re: vim won't start on new installation.

#6 2023-09-07 10:05:15

Re: vim won't start on new installation.

#7 2023-09-07 10:09:19

Re: vim won't start on new installation.

Board footer