Hi Michael, Thanks for your help, and for your quick reply. I agree, the -arch ppc is a big part of the problem, maybe all of it. If in fact ARM files are being generated, then the problem is worse than I imagined. I think that issue was caused by "crossing the beams", using one compiler, mixed with other tools and sources. I think one tool generated PPC code, and another could not deal.
Unfortunately all that does not help much when trying to understand the root cause of the build issues. I have been unable to find the letters ppc anywhere in the cx_freeze code, so the root problem probably is not there. My best guess at this point is that the issues are all in the Python build tools for OSX. They should not be building FAT bits for OSX 10.6. OK, I think I got it figured out. It sucks, but it is simple. I am using python 2.6.6 (job requirement). Therefore I am using the python.org Mac OSX 10.3 binary install. Hence the FAT output. This SHOULD NOT happen when building on OSX 10.6, which is an Intel only OS (there is no FAT, there is no PPC, in this universe). All of the OSX binaries of python.org builds (including python 3.x) are 10.3 compatible, which means they may not be 10.6 compatible. ARGH! It is possible that at some point between 2.6.6 and 3.2, the python.org folks figured all this out, and everything works if I can just install the right binaries. I'm not sure about the reaction to straying from 2.6.6. If it solves all issues, and does not generate others, all will be good... I may have to build python from sources to use 2.6.6. Not looking forward to that. I am moving this to python.org for now... I will try to reply to the other posting of this issue which I saw yesterday here on cx_freeze also. Thank you! --Dave On 5/23/11 11:29 PM, "Michael Wood" <[email protected]> wrote: >Hi > >On 24 May 2011 05:00, Dave McGary <[email protected]> wrote: >[...] >> PS - Here is the relevant text from monitorŠ >> $ python setup.py build >[...] >> building 'cx_Freeze.util' extension >> creating build/temp.macosx-10.6-fat-2.6/source >> gcc-4.0 -fno-strict-aliasing -fno-common -dynamic -arch ppc -arch i386 >>-g > >The "-arch ppc" line is what's tripping you up. I don't know where >that is defined. Also, I have not tried Xcode 4 yet. See if you can >get around the problem by manually running that command (perhaps with >gcc-4.2 instead) without the "-arch ppc" part and then see if you can >continue the build from there. Not sure that will work, though. > >> -O2 -DNDEBUG -g -O3 >> -I/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 -c >> source/util.c -o build/temp.macosx-10.6-fat-2.6/source/util.o >[...] >> OK, realizing my possible mistake, I try an experiment. >> 3) Remove the soft link of >> 4) sudo ln -s >> /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/gcc-4.0 >> /usr/bin/gcc-4.0 > >No, I think this is barking up the wrong tree. This compiler most >likely create ARM binaries for running on the iPhone and not on your >Intel Mac. > >> Here I may have crossed things up badly. Using a single tool from one >>area, >> and everything else from elsewhere. >> NOW I get the error I have seen in the archive, but have not seen FIXED >>in >> the archives. At least I know I am no longer aloneŠ >> I am now getting: lipo: can't figure out the architecture type of: >> /var/folders/gY/gY+p1oTwEcCtFzSEJM0A9++++TI/-Tmp-//ccSJXe5M.out > >Yes, I suspect this is because that copy of lipo knows about the Intel >architecture (and maybe PPC) but not ARM. > >> Š >> Š >> Š >> building 'cx_Freeze.util' extension >> gcc-4.0 -fno-strict-aliasing -fno-common -dynamic -arch ppc -arch i386 >>-g >> -O2 -DNDEBUG -g -O3 >> -I/Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 -c >> source/util.c -o build/temp.macosx-10.6-fat-2.6/source/util.o >> gcc-4.0: installation problem, cannot exec >> >>'/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/powerpc-apple-d >>arwin10-gcc-4.0.1': >> No such file or directory > >This is because of the "-arch ppc" again, but this time it can't find >a PPC version of the compiler, whereas the earlier error was >complaining about the assembler rather than the compiler itself. > >> lipo: can't figure out the architecture type of: >> /var/folders/gY/gY+p1oTwEcCtFzSEJM0A9++++TI/-Tmp-//ccSJXe5M.out >> error: command 'gcc-4.0' failed with exit status 255 >> >> Is there a global I can set to turn off the attempt to make both FAT >>and PPC >> versions of everything? > >I suspect this is something to do with how setup tools works and not >specific to cx_Freeze. > >> I tried setting Target to OSX 10.6, that only got rid of one warning, >>the >> attempts to build FAT versions (and the expected failures) goes on. >> I look forward to your responses. >> Thank you! >> --Dave > >-- >Michael Wood <[email protected]> > >-------------------------------------------------------------------------- >---- >vRanger cuts backup time in half-while increasing security. >With the market-leading solution for virtual backup and recovery, >you get blazing-fast, flexible, and affordable data protection. >Download your free trial now. >http://p.sf.net/sfu/quest-d2dcopy1 >_______________________________________________ >cx-freeze-users mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/cx-freeze-users ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ cx-freeze-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
