Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 346193 - Fresh install, app-editors/vim-7.2.442 missing dev-lang/perl-5.12.2-r2
Summary: Fresh install, app-editors/vim-7.2.442 missing dev-lang/perl-5.12.2-r2
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: AMD64 Linux
: High minor
Assignee: Vim Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-20 16:11 UTC by James Ashley
Modified: 2011-03-02 08:23 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Ashley 2010-11-20 16:11:41 UTC
This may be someone else's problem entirely. I had slicehost create a new gentoo image for me. Did the various emerge -update -world steps to get the latest versions of everything (I think...it's been quite a while since I messed with gentoo).

Tried to run vim, got the error "vim: error while loading shared libraries: libperl.so.1: cannot open shared object file: No such file or directory"

/usr/lib has libperl.so.5.12.2 and a couple of symlinks pointing at it (libperl.so.5.12 and libperl.so).

Added the missing symlink and vim ran fine. No big deal, and something anyone who's gutsy enough to try gentoo should be able to fix instantly, but I figured it was worth mentioning.

Reproducible: Always

Steps to Reproduce:
1. Set up a fresh install
2. Try to run vim

Actual Results:  
vim: error while loading shared libraries: libperl.so.1: cannot open shared object file: No such file or directory

Expected Results:  
Text editing
Comment 1 Tim Harder gentoo-dev 2011-03-02 08:23:05 UTC
I don't think this is an issue anymore. At least, libperl.so.1 doesn't exist on any machines I have access to. Perhaps the original image had vim built against a perl library that wasn't present in the image. Therefore, if you had run revdep-rebuild or something similar the problem might have been fixed.

Closing as invalid. Feel free to reopen if you can reproduce this or provide more information.