[Pythonmac-SIG] Running "freeze" on non-framework Python/universal binary issues

Bob Ippolito bob at redivi.com
Thu Jul 20 19:50:56 CEST 2006


On Jul 20, 2006, at 9:54 AM, Kevin Walzer wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I'm trying to learn how to "freeze" an application that links  
> against a
> non-framework build of Python. The basic mechanism works fine when  
> I try
>  a vanilla install of PPC Python 2.4 via Fink:
>
> /sw/bin/python freeze.py hello.py
> ...lots of messages
> make
> ....lots more messages
> ./hello
> Hello world...
> Kevin-Walzers-Computer:~/python24-fat/Tools/freeze kevin$ file hello
> hello: Mach-O executable ppc
>
> "freeze" is having problems with my non-framework "universal" build of
> Python 2.4, however. It seems to be gagging on the "arch" flags.  
> Here's
> a typical error message:
>
> /usr/bin/ld: warning M_rfc822.o cputype (18, architecture ppc) does  
> not
> match cputype (7) for specified -arch flag: i386 (file not loaded)
>
> I probably need to figure out a way to get the right flags passed  
> on to
> "freeze" or "make" so that the i386 object files are built also; right
> now it's only outputting ppc files. Here's the command that runs:
>
> gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes
> - -I/usr/local/python-unix/include/python2.4
> - -I/usr/local/python-unix/include/python2.4 -c M_traceback.c
>
>
> Any advice?
>
> (I'm trying "freeze" because py2app doesn't seem to play nicely with
> non-framework builds, and I have no clue how to fix it.)

The other question is why the heck are you using a non-framework build?

You may have better luck with cx_Freeze than the built-in freeze  
tool. I've never tried either on Mac OS X.

-bob



More information about the Pythonmac-SIG mailing list