https://bugzilla.novell.com/show_bug.cgi?id=385376 Summary: Package 'python' does not build correctly on PPC64 Product: openSUSE 10.2 Version: Final Platform: PowerPC-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pth@novell.com ReportedBy: sergiodj@linux.vnet.ibm.com QAContact: qa@suse.de Found By: --- Hi, I'm currently trying to build the last version of Python's src.rpm (namely python-2.5-19.6.src.rpm) on a biarch machine (i.e., 64-bit kernel and mostly 32-bit userspace apps). The 32-bit build works properly: #> rpmbuild --target ppc -bb SPECS/python.spec << OK >> What happens is that, when I try to build it for PPC64, some errors occurs: #> rpmbuild --target ppc64 -bb SPECS/python.spec .. Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Requires: python = 2.5 libc.so.6()(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) libpthread.so.0()(64bit) libpython2.5.so.1.0()(64bit) RPM build errors: File not found: /var/tmp/python-2.5-build/usr/lib64/python2.5/lib-dynload/_sqlite3.so Note that Python got compiled successfuly, and all the tests were done without errors. Only after that this error came up. I'd like to know what can be done to fix this. Actually, what's happening is that I don't have (and haven't found) the package sqlite3 for PPC64. I've also tried to build it from its src.rpm, but fell in another dependency case and gave up. Obs.: I've made a tiny modification on Python's spec file in order to be able to compile it for PPC64: --- SPECS/python.spec 2008-01-10 09:59:23.000000000 -0800 +++ SPECS/python.spec.new 2008-04-30 11:11:49.000000000 -0700 @@ -217,6 +217,9 @@ # use rpm_opt_flags ######################################## export OPT="$RPM_OPT_FLAGS" +%ifarch ppc64 ia64 +export CC="gcc -m64" +%endif ######################################## # regenerate ######################################## -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.