Bug 731295 - meshlab-1.3.0a-1.fc15 (updates-testing) error loading shared library
Summary: meshlab-1.3.0a-1.fc15 (updates-testing) error loading shared library
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: meshlab
Version: 15
Hardware: i386
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Eric Smith
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-17 09:54 UTC by Colin Macdonald
Modified: 2011-11-10 08:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-10 08:50:27 UTC


Attachments (Terms of Use)

Description Colin Macdonald 2011-08-17 09:54:38 UTC
An update to meshlab is in updates-testing (meshlab-1.3.0a-1.fc15).  It fails to run saying it can't find libcommon.so.1, which on my system is in /usr/lib/meshlab.

Downgrading to the previous version works fine.

$ meshlab
meshlab: error while loading shared libraries: libcommon.so.1: cannot open shared object file: No such file or directory

$ locate -i libcommon.so
/usr/lib/htdig/libcommon.so
/usr/lib/meshlab/libcommon.so
/usr/lib/meshlab/libcommon.so.1
/usr/lib/meshlab/libcommon.so.1.0
/usr/lib/meshlab/libcommon.so.1.0.0

Comment 1 Susi Lehtola 2011-08-17 11:08:09 UTC
Obviously "libcommon" is such a common file name, that the library has been placed in a separate location so that it would not clash with other libraries of the same name. As you can see, even you have two completely different versions of it.

Anyway, the meshlink binary should have an rpath to %{_libdir}/meshlab to make it find its version of libcommon.

Comment 2 Eric Smith 2011-08-17 17:14:19 UTC
I'll add rpath to the link, but for now I've unpushed this update, which has as yet unresolved FTBFS problems on FC16 and rawhide.

Comment 3 Eric Smith 2011-11-10 08:50:27 UTC
Fixed in meshlab-1.3.1-2 in rawhide and in F15 and F16 updates.


Note You need to log in before you can comment on or make changes to this bug.