On 9 Apr, 2007, at 6:59, Bob Ippolito wrote:
I'm pretty sure that 10.4 would fix this. 10.3.9 isn't really equipped to build extensions for a universal Python (it can only build the PPC part). It runs them fine, but it can't build stuff properly because the Xcode is too old.
You can't build universal binaries on 10.3.9, but I'd expect that you can build ppc-only extensions on 10.3.9 as long as you don't explictly link to Python.framework. Adding MACOSX_DEPLOYMENT_TARGET=10.3 to environment before linking might help as well (the symbols that give link errors are weakly linked which isn't supported on the default deployment target).
Ronald
-bob On 4/8/07, David Pratt <[EMAIL PROTECTED]> wrote:Hi Bob. My apologies. I am using 10.3.9. If you require any furtherdetails, please let me know. I use this mac for development and this isreally not good. I have ordered a copy of 10.4.9 that I hope will be arriving within the week to try but I am on a PPC.I scanned the list quickly and noticed another post from someone a whileback. from Stephan Werner 4/07/06 /usr/bin/ld: Undefined symbols: _fstatvfs referenced from Python expected to be defined in libSystem _lchown referenced from Python expected to be defined in libSystem _statvfs referenced from Python expected to be defined in libSystem This happens only for the PPC part of my UB application, it seems to link the i386 part just fine. I am using the 10.3.9 SDK for the PPC side, 10.4u for i386. Do I need to link against the 10.4u SDK on both sides? I'd not be too happy about doing that, since I want to make sure the app runs perfeclty on 10.3.9/PPC. Googling I see others with posts to different software lists for the software they are trying to build. Regards, David Bob Ippolito wrote:On 4/8/07, David Pratt <[EMAIL PROTECTED]> wrote:I have been getting the same undefined symbols when linking after compiling. On a few weeks back I posted on a problem buildingmod_python, now its pylucene - same problem. Crazy thing is I build the same pylucene version just before upgrading to 2.4.4 pythonmac withoutthese problems. From mod_python build: ld: Undefined symbols:_fstatvfs referenced from Python expected to be defined in libSystem_lchown referenced from Python expected to be defined in libSystem _statvfs referenced from Python expected to be defined in libSystem apxs:Error: Command failed with rc=65536 . make[1]: *** [mod_python.so] Error 1 make: *** [do_dso] Error 2 From pylucene build: ld: Undefined symbols:_fstatvfs referenced from Python expected to be defined in libSystem_lchown referenced from Python expected to be defined in libSystem _statvfs referenced from Python expected to be defined in libSystem gmake: *** [release/_PyLucene.so] Error 1I have googled to see what more I can find and there are others withthis issue but maybe it is the fact that folks are doing infrequentsoftware builds that is leaving this problem under the surface. Does anyone have any suggestions. All seemed good when I was on the PPC pythonmac at 2.4.3The version of OS X you're using is probably relevant. -bob_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
