This is a tracker bug in accordance with the Packaging Guidelines. According to upstream[1]: > The MongoDB server (mongod) must run on a little-endian CPU, so if you are using a PPC OS X machine, mongod will not work. [1] http://www.mongodb.org/downloads
*** Bug 637262 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.
I tried building from the source rpm in Fedora EPEL 6 on ppc64 and s390x and they both fail: http://rpmfind.net//linux/RPM/epel/6/x86_64/pymongo-2.1.1-1.el6.x86_64.html Here is one error from s390x: + CFLAGS='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -march=z9-109 -mtune=z10' + /usr/bin/python setup.py build ***************************************************** The optional C extensions are currently not supported on big endian platforms and will not be built. Performance may be degraded. ***************************************************** It was also failing with this: chmod: cannot access `/home/esbld/rpmbuild-pymongo/BUILDROOT/pymongo-2.2.1-1.ibm.s390x/usr/lib64/python2.6/site-packages/pymongo/_cmessage.so': No such file or directory and this: RPM build errors: File not found: /home/esbld/rpmbuild-pymongo/BUILDROOT/pymongo-2.2.1-1.ibm.s390x/usr/lib64/python2.6/site-packages/pymongo File not found by glob: /home/esbld/rpmbuild-pymongo/BUILDROOT/pymongo-2.2.1-1.ibm.s390x/usr/lib64/python2.6/site-packages/pymongo-2.2.1-*.egg-info Note that I had updated the source tar.gz from version 2.1.1 to 2.2.1 from PyPI but it didn't make a difference.
Matt, I think the reason is that the _cmessage.so module is not built per the message you saw. This directly explain the first error. And the result of the first "error" is that the package is now arch independent and thus uses /usr/lib/python2.x/site-packages instead of /usr/lib64/... for the 64-bit arches. And lets move the discussion to the mailing list (https://lists.fedoraproject.org/mailman/listinfo/ppc or https://lists.fedoraproject.org/mailman/listinfo/s390x), bugzilla is not the best place. Although this bug is about mongodb itself (where the situation hasn't change AFAIK) and not about the python interface for it.
Upstream plans big-endian support at the end of 2016 year <https://jira.mongodb.org/browse/SERVER-1625>. E.g. Perl client already contains some preliminary code. I have no idea what network format is used, but provided clients can run on different hosts than localhost, I would be for lifting the ExcludeArch constraint from clients.