Bug 438749 - Guile does not load 64-bit libguile-cairo.so.0 from /usr/lib64/
Guile does not load 64-bit libguile-cairo.so.0 from /usr/lib64/
Product: Fedora
Classification: Fedora
Component: guile-cairo (Show other bugs)
x86_64 Linux
low Severity urgent
: ---
: ---
Assigned To: Xavier Lamien
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-03-24 16:54 EDT by Rajesh Krishnan
Modified: 2009-01-09 01:14 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 01:14:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rajesh Krishnan 2008-03-24 16:54:26 EDT
Description of problem:
On x86_64 machines, guile should load libraries from /usr/lib64/ and NOT 
(only) from /usr/lib/.

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

How reproducible:
Steps to Reproduce:

1.  On an x86_64 machine, install both guile.x86_64 and guile-cairo.x86_64.

2.  Execute the following on the command line and notice the error:
  $ guile -c "(use-modules (cairo))"
ERROR: In procedure dynamic-link:
ERROR: file: "/usr/lib/libguile-cairo", message: "/usr/lib/libguile-cairo.so: 
cannot open shared object file: No such file or directory"

Actual results:
ERROR: file: "/usr/lib/libguile-cairo", message: "/usr/lib/libguile-cairo.so: 
cannot open shared object file: No such file or directory"

Expected results:
The command should not display any error message.

Additional info:
1.  cd to the /usr/lib/ directory.
2.  Create a symlink from /usr/lib64/libguile-cairo.so.0 
to /usr/lib/libguile-cairo.so:

$ cd /usr/lib/
$ ln -s ../lib64/libguile-cairo.so.0 libguile-cairo.so

This would temporarily fix the problem, but is NOT a solution, because it 
would screw up the 32-bit guile utility if installed and used with the 32-bit 

Potential Solutions:
1.  Make sure that the x86_64 version of /usr/bin/guile loads all 3rd-party 
libraries from /usr/lib64/ and NOT from /usr/lib (this points to a guile 
packaging problem).  

2.  Make sure there exists a symlink from /usr/lib64/libguile-cairo.so.0 
to /usr/lib64/libguile-cairo.so.  (this points to a libguile-cairo packaging 
Comment 1 Xavier Lamien 2008-03-25 03:39:53 EDT
Comment 2 Bug Zapper 2008-11-26 05:15:34 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Bug Zapper 2009-01-09 01:14:57 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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