Bug 98226
Summary: | liboctinterp.so not in search path / installation directory? | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Jaakko R <jaakkor2> |
Component: | octave | Assignee: | Lon Hohberger <lhh> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i586 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-07-30 21:40:44 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 100643 |
Description
Jaakko R
2003-06-28 08:57:28 UTC
octave-2.1.49-4 will appear in rawhide soon. In the mean time, you may download them from my people.redhat.com page: http://people.redhat.com/lhh/octave-2.1.49-4.i386.rpm http://people.redhat.com/lhh/octave-2.1.49-4.src.rpm Let me know if it works for you. $ rpm -q octave octave-2.1.49-4 $ rpm -q glibc glibc-2.3.2-27.9 $ octave octave: relocation error: /usr/lib/liboctinterp.so: symbol sys_siglist, version GLIBC_2.3.3 not defined in file libc.so.6 with link time reference $ strings /lib/libc.so.6 | grep GLIBC_2.3.3 GLIBC_2.3.3 Hmm, maybe more uptodate glibc is needed than the one from RH9? Oddly enough, I do not see that version of glibc in Raw Hide at the moment. Anyway, all the new octave package does differently than the old one is set up symlinks in /usr/lib: /usr/lib/liboctinterp.so => /usr/lib/octave-2.1.49/liboctinterp.so.2.1.49 and the like. You can always add: /usr/lib/octave-2.1.49 to /etc/ld.so.conf (don't forget to run "ldconfig" when you're done!). Either of these should make the old package (2.1.49-2) work as well as can be (...being bleeding edge software). Perhaps with the new /etc/ld.so.conf.d/ structure, octave can safely add %{_libdir}/octave-%{version} to a file there and avoid the silly linking - which appears to break when doing an upgrade of the octave package. |