In article <nad-61009a.17150922022...@news.gmane.org>, Ned Deily <n...@acm.org> wrote: > In article <4d640175$0$81482$e4fe5...@news.xs4all.nl>, > Irmen de Jong <ir...@-nospam-xs4all.nl> wrote: > > However, I'm having trouble compiling a framework build from source on > > Mac OS 10.5.8 on PowerPC. No matter what I try (gcc 4.0, gcc 4.2, > > different compiler options), the compilation aborts with the following > > error: > > > > Undefined symbols: > > "___fixdfdi", referenced from: > > _rlock_acquire in libpython3.2m.a(_threadmodule.o) > > _lock_PyThread_acquire_lock in libpython3.2m.a(_threadmodule.o) > > "___moddi3", referenced from: > > _PyThread_acquire_lock_timed in libpython3.2m.a(thread.o) > > _acquire_timed in libpython3.2m.a(_threadmodule.o) > > "___divdi3", referenced from: > > _PyThread_acquire_lock_timed in libpython3.2m.a(thread.o) > > _acquire_timed in libpython3.2m.a(_threadmodule.o) > > ld: symbol(s) not found > > /usr/bin/libtool: internal link edit command failed > > Unfortunately, this is a variation of an old issue that hasn't yet been > fixed (http://bugs.python.org/issue1099).
UPDATE: this problem has been fixed in the newly-release Python 3.2.1. On a 10.4 or 10.5 PPC machine, you should now be able to successfully build a PPC-only 3.2 framework with just: ./configure --enable-framework ; make On 10.5, you may want to use: ./configure --enable-framework MACOSX_DEPLOYMENT_TARGET=10.5 ; make -- Ned Deily, n...@acm.org -- http://mail.python.org/mailman/listinfo/python-list
