Red Hat Bugzilla – Bug 448318
Not 64 bits clean
Last modified: 2011-11-24 21:06:14 EST
Description of problem:
Library don't seem to be 64 bits clean, strange results on x86_64 host.
Upstream is working on the problem.
Could also improve the package by including the tcl tool.
Also seems to have problems on sparcv9, breaking msort on sparcv9 too.
This bug has been triaged
Please provide a link to the upstream bug
Upstream has not implemented support for x86_64.
This is a bug to track that issue.
Debian has a fix for the borked libuninum on x86_64. I ported the patch and cleaned up the spec. Commits on top of our current version can be pulled from
and browsed at
Even after a rebuild with this, msort has problems sorting roman numerals such as IX, so msort may have independent issues. But the libuninum fix is worth it nonetheless.
What is the needed git magic to merge this nice changes?
libuninum-2.7-9.fc15 has been submitted as an update for Fedora 15.
libuninum-2.7-9.fc14 has been submitted as an update for Fedora 14.
libuninum-2.7-9.fc16 has been submitted as an update for Fedora 16.
(In reply to comment #5)
> Great, thanks!
> What is the needed git magic to merge this nice changes?
I see you figured it out ;)
Sorry for the botched version number in the changelog; I got too eager on trimming down the digits in 2.7-7.1...
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libuninum-2.7-9.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
libuninum-2.7-9.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
libuninum-2.7-9.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
libuninum-2.7-9.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.