Bug 32752 - vim: Symbol `ospeed' has different size in shared object, consider re-linking
Summary: vim: Symbol `ospeed' has different size in shared object, consider re-linking
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: vim
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-22 23:43 UTC by Martin C. Messer
Modified: 2007-04-18 16:32 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-03-28 13:05:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Martin C. Messer 2001-03-22 23:43:55 UTC
vim: Symbol `ospeed' has different size in shared object, consider
re-linking

I get the above error when I close vim after editing a file. I have just
applied the latest vim errata: 

[root@evelle /root]# rpm -qa | grep vim 
vim-minimal-5.7-8
vim-common-5.7-8
vim-enhanced-5.7-8
vim-X11-5.7-8

Comment 1 Zvi Har'El 2001-03-28 11:04:31 UTC
rebuilding the vim package solves the problem:
 cd /usr/src/redhat/SRPMS
 rpm --rebuild vim-5.7-8.src.rpm
 cd /usr/src/redhat/RPMS/i386
 rpm --force -Uvh vim*


Comment 2 Martin C. Messer 2001-03-28 13:05:49 UTC
Confirmed.

Comment 3 David Lawrence 2001-03-28 16:44:48 UTC
Verified this problem to occur with vim-minimal-5.7-8. This problem though does
seem to be fixed in our latest version of vim available either from rawhide or
in our latest beta called 'wolverine'. Her are the newest package names.

vim-common-6.0-0.26.i386.rpm    vim-minimal-6.0-0.26.i386.rpm
vim-enhanced-6.0-0.26.i386.rpm  vim-X11-6.0-0.26.i386.rpm

You can probably get these from ftp://rawhide.redhat.com


Comment 4 Andreas M. Kirchwitz 2001-03-28 21:11:04 UTC
Hmm,

I have the same problem with the new "vim" package (5.7-8) on all
RedHat 7.0 boxes. But installing a rawhide package with an experimental
version or rebuilding a package manually is not what I'd call a "resolved"
bug. ;-)

Will there be an updated version of the "vim" package with a fixed binary?

Regards,
Andreas


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