Talk:Release notes/13.2.1: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 28: | Line 28: | ||
Conclusion: an application claims libc.so.6 is absent; yum claims it is |
Conclusion: an application claims libc.so.6 is absent; yum claims it is |
||
present. |
present. |
||
:Yum is not relying on an actual test for presence of libc.so.6, but is relying on the history of the package system, so this method of using yum is not entirely reliable. However, libc.so.6 is required before yum can run this test, so it does prove libc.so.6 is present. Whether it is present or not may not be relevant to the problem; there's no error from your application suggesting the file is missing. --[[User:Quozl|Quozl]] 03:41, 29 September 2014 (UTC) |
|||
For reference, no such problem in OLPC 13.2.0 or in Debian Wheezy. |
For reference, no such problem in OLPC 13.2.0 or in Debian Wheezy. |
||
| Line 34: | Line 35: | ||
Ideas? Thanks,       ... Peter E. |
Ideas? Thanks,       ... Peter E. |
||
:Fix the application? Examine the source code of the application to find out why it is opening the file. Change the source code to report further details of the failure to open the file. Use strace to find what syscalls are failing. Repeat the installation as root. --[[User:Quozl|Quozl]] 03:14, 29 September 2014 (UTC) |
:Fix the application? Examine the source code of the application to find out why it is opening the file. Change the source code to report further details of the failure to open the file. Use strace to find what syscalls are failing. Repeat the installation as root. --[[User:Quozl|Quozl]] 03:14, 29 September 2014 (UTC) |
||
::Discussion has moved to [http://lists.laptop.org/pipermail/devel/2014-November/038674.html mailing list] --[[User:Quozl|Quozl]] 02:26, 10 November 2014 (UTC) |
|||
Latest revision as of 02:26, 10 November 2014
libc.so.6 in 13.2.1
Installed 13.2.1 and an application named aos. In gnome terminal, came to this.
[olpc@xo-53-1d-bb ~]$ aos Unix.Dlopen: loading library libc.so.6 failed ... [olpc@xo-53-1d-bb ~]$ su bash-4.2# yum provides libc.so.6 glibc-2.16-24.fc18.i686 : The GNU libc libraries Repo : fedora Matched from: Provides : libc.so.6 glibc-2.16-34.fc18.i686 : The GNU libc libraries Repo : updates Matched from: Provides : libc.so.6 glibc-2.16-34.fc18.i686 : The GNU libc libraries Repo : @updates Matched from: Provides : libc.so.6 bash-4.2# yum install glibc-2.16-34.fc18.i686 Package glibc-2.16-34.fc18.i686 already installed and latest version Nothing to do
Conclusion: an application claims libc.so.6 is absent; yum claims it is present.
- Yum is not relying on an actual test for presence of libc.so.6, but is relying on the history of the package system, so this method of using yum is not entirely reliable. However, libc.so.6 is required before yum can run this test, so it does prove libc.so.6 is present. Whether it is present or not may not be relevant to the problem; there's no error from your application suggesting the file is missing. --Quozl 03:41, 29 September 2014 (UTC)
For reference, no such problem in OLPC 13.2.0 or in Debian Wheezy.
Ideas? Thanks, ... Peter E.
- Fix the application? Examine the source code of the application to find out why it is opening the file. Change the source code to report further details of the failure to open the file. Use strace to find what syscalls are failing. Repeat the installation as root. --Quozl 03:14, 29 September 2014 (UTC)
- Discussion has moved to mailing list --Quozl 02:26, 10 November 2014 (UTC)