On 20/03/2010, at 1:20 AM, Stuart Edwards wrote:
Tried to package the Intel Aqua build and ran into the following which raises a couple of points:
../../../python//ppc/2.5/numpy-1.0.4-py2.5.egg-info -> Inkscape.app/Contents/Resources/python/site-packages/ppc/2.5/numpy-1.0.4-py2.5.egg-info cp: /opt/local/etc/pango/pangox.aliases: No such file or directory Looking for dependencies. Round 1 Looking for dependencies. Round 2 Looking for dependencies. Round 3 Could not rewrite dylb paths for bundled libraries. This requires Macports to be installed in a PREFIX of at least 50 characters in length.
The package will still work if the following line is uncommented in Inkscape.app/Contents/Resources/bin/inkscape: export DYLD_LIBRARY_PATH="$TOP/lib"
Application bundle creation failed
- My opt/local/etc/pango contains only pango.modules and pangorc. There is a pangox.aliases in the original download file for pango 1.26 but the local portfile process did not include its installation in opt/---
Strange. I'm using pango 1.24.5 on my build machine, and a "port contents pango" show that file as being installed by pango. Don't know why this shouldn't be the case for you too.
- I've seen the 50 character requirement mentioned in other posts - but not sure how to accomplish this with an OSX macports install that doesn't ask a whole lot of questions about where to put things. Since I don't use macports for anything else I just have the one tree that was installed for the Inkscape effort. Can I just rename it - or duplicate it with a 50 char name?
You can install a new Macports tree from source by downloading the source package and then doing: ./configure --prefix=/opt/local-macports-with-a-really-long-directory-name/ make sudo make install
You can't just rename the directory containing an existing macports tree as a lot of the libraries and config file have hardcoded paths in them at this point. Sorry, but you really have to do this from scratch!
- The export DYLD_------ line is already uncommented in the script - I assume this is normal ( but the package doesn't work - presumably because of 1 and 2.
It's definitely still commented out in the repository in the current head. Perhaps you uncommented it previously in your local copy?
Cheers, Michael