[Pythonmac-SIG] [ANN] py2app 0.3.2

Bob Ippolito bob at redivi.com
Sat Jul 22 23:36:52 CEST 2006


On Jul 21, 2006, at 3:18 PM, Kaweh Kazemi wrote:

>>> WARNING: Mach-O header may be too large to relocate
>>> Traceback (most recent call last):
>>>    File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
>>> python2.4/site-packages/py2app-0.3.2-py2.4.egg/py2app/build_app.py",
>>> line 548, in _run
>>>      self.run_normal()
>>>    File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
>>> python2.4/site-packages/py2app-0.3.2-py2.4.egg/py2app/build_app.py",
>>> line 619, in run_normal
>>>      self.create_binaries(py_files, pkgdirs, extensions,  
>>> loader_files)
>>>    File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
>>> python2.4/site-packages/py2app-0.3.2-py2.4.egg/py2app/build_app.py",
>>> line 732, in create_binaries
>>>      platfiles = mm.run()
>>>    File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
>>> python2.4/site-packages/macholib-1.1-py2.4.egg/macholib/
>>> MachOStandalone.py", line 135, in run
>>>    File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
>>> python2.4/site-packages/macholib-1.1-py2.4.egg/macholib/MachO.py",
>>> line 111, in write
>>>    File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
>>> python2.4/site-packages/macholib-1.1-py2.4.egg/macholib/MachO.py",
>>> line 302, in write
>>>    File "/Library/Frameworks/Python.framework/Versions/2.4/lib/
>>> python2.4/site-packages/macholib-1.1-py2.4.egg/macholib/MachO.py",
>>> line 292, in synchronize_size
>>> ValueError: New Mach-O header is too large to relocate
>>>> /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/
>>> site-packages/macholib-1.1-py2.4.egg/macholib/MachO.py(292)
>>> synchronize_size()
>>>
>>>
>>> i'm trying to include a custom made library into my application. i'm
>>> not assuming that py2app (or macholib) is the problem here, but the
>>> library, though i was hoping that this error-message could give
>>> someone a clue where i could look to solve my problem.
>>>
>>> any hints are much appreciated.
>>
>> Some Mach-O don't have enough room leftover to rewrite their load  
>> commands. This is quite rare, but you may have to re-link the  
>> library with -headerpad_max_install_names. It could otherwise be a  
>> bug in macholib, but I wouldn't be able to say without a copy of  
>> the library.
>
> thanks a lot. i will give that a try and re-link the libraries.
>
> essentially i am trying to package a Panda3D test application using  
> py2app - see http://knuddl.net/moin.cgi/InstallPanda3d for my  
> Panda3D package if interested(compiled/linked for OS X including  
> installation instructions) - though be aware that the installation  
> is still cumbersome and definitely not as user friendly as i would  
> like it to be - this is still very experimental (Panda3D has no  
> official OS X support yet); anyways, i'll re-link the libraries and  
> see how it's going.

The "loader problem" documented in that wiki isn't a Mac OS X problem  
per se, it's just what PythonLauncher does. It launches scripts with  
a path of $HOME. Pretty stupid, but that's what it does. It's only  
relevant if you're double-clicking .py files from the finder.

-bob



More information about the Pythonmac-SIG mailing list