Bug 119562

Summary: xemacs wants older Canna
Product: [Fedora] Fedora Reporter: Kaj J. Niemi <kajtzu>
Component: xemacsAssignee: Jens Petersen <petersen>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: tagoh
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-04-08 05:47:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Kaj J. Niemi 2004-03-31 13:34:02 UTC
Description of problem:
I think xemacs needs to be recompiled against the newer Canna although
the dynamic library versions seem to have gone backwards (newer
package version 1, older 1.2)

Version-Release number of selected component (if applicable):

% rpm -qp --provides Canna-libs-3.7p1-6.i386.rpm
Canna-libs = 3.7p1-6

Steps to Reproduce:
1. rpm -Fvh Canna*3.7p1-6*
error: Failed dependencies:
        libRKC.so.1.2 is needed by (installed) xemacs-21.4.15-3
        libcanna.so.1.2 is needed by (installed) xemacs-21.4.15-3

Thanks :)

Comment 1 Jens Petersen 2004-03-31 14:24:37 UTC
I believe this happened when Canna was updated with xmkmf from xorg-x11.

Tagoh, is the right solution to change Canna or rebuild xemacs?

Comment 2 Akira TAGOH 2004-04-01 00:42:41 UTC
Jens, Canna has no idea to solve this as long as it uses the changed
xmkmf. the core part is including the ld options like -soname is
generated by xmkmf. just having libcanna.so.1.2 doesn't help so that
-soname has a decision for the soname you know. IOW current behavior
of xmkmf looks like libtool does. and I believe changing the minor
version of the soname shouldn't affects anything. so depending on
lib*.so.n is right, and rebuilding xemacs is the right solution then.

Comment 3 Jens Petersen 2004-04-01 11:18:57 UTC
Thanks, should get fixed in next build.

Comment 4 Jens Petersen 2004-04-06 15:47:54 UTC
Should be fixed in 21.4.15-4.

Comment 5 Kaj J. Niemi 2004-04-08 05:47:51 UTC
Is fixed. Thanks. :)