Bug 23068 - Symbol `ospeed' has different size in shared object, consider re-linking
Summary: Symbol `ospeed' has different size in shared object, consider re-linking
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: ncurses (Show other bugs)
(Show other bugs)
Version: 1.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-01 02:48 UTC by Bill Crawford
Modified: 2007-04-18 16:30 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-01-01 02:50:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Bill Crawford 2001-01-01 02:48:04 UTC
[root@localhost linus-2.4.0-test13-pre7]# info
info: Symbol `ospeed' has different size in shared object, consider
re-linking
[root@localhost linus-2.4.0-test13-pre7]# ldd /usr/bin/info
        libncurses.so.5 => /usr/lib/libncurses.so.5 (0x40029000)
        libc.so.6 => /lib/libc.so.6 (0x4006b000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
[root@localhost linus-2.4.0-test13-pre7]# nm /usr/lib/libncurses.so.5
nm: /usr/lib/libncurses.so.5: no symbols

Not sure quite where the fault lies, but ... binary incompatability rears
its ugly head.
This may bite people with any non-distro apps linked against this library.
Is this a change in ncurses to reflect a standard API ?

Comment 1 Bill Crawford 2001-01-01 02:50:21 UTC
Forgot package versions:

[root@localhost linus-2.4.0-test13-pre7]# rpm -qf /usr/lib/libncurses.so.5.2
ncurses-5.2-2
[root@localhost linus-2.4.0-test13-pre7]# rpm -q info
info-4.0-17


Comment 2 Bernhard Rosenkraenzer 2001-01-01 10:54:13 UTC
It was a bug in ncurses - A change without a real reason. We've reverted this
particular change in 5.2-3.



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