Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OS X Dylibbundler Error #197

Closed
airscout opened this issue Jul 6, 2013 · 2 comments
Closed

OS X Dylibbundler Error #197

airscout opened this issue Jul 6, 2013 · 2 comments

Comments

@airscout
Copy link

airscout commented Jul 6, 2013

I haven't been able to bundle the app package because of the header padding issue, but the culprit in my case seems to be in GTK+ and not Pango. No luck with "headerpad_max_install_names" and a recompile of GTK+. Full output here.

install_name_tool: changing install names or rpaths can't be redone for: target/GtkRadiant.app/Contents/Resources/lib/gtk-2.0/2.10.0/immodules/im-multipress.so (for architecture x86_64) because larger updated load commands do not fit (the program must be relinked, and you may need to use -headerpad or -headerpad_max_install_names)

Error : An error occured while trying to fix depencies of target/GtkRadiant.app/Contents/Resources/lib/gtk-2.0/2.10.0/immodules/im-multipress.so
make: *** [bundle] Error 1

I have noticed that bundling seems to take nearly as long as the compile and Dylibbundler spews about 280 warnings (which turn out to be repeats of the same 7 complaints). I'm not sure if either is normal.

/!\ WARNING : Cannot resolve symlink '/opt/local/lib/libbz2.1.0.dylib '
/!\ WARNING : Cannot resolve symlink '/opt/local/lib/libgdkglext-x11-1.0.0.dylib '
/!\ WARNING : Cannot resolve symlink '/opt/local/lib/libgraphite2.3.dylib '
/!\ WARNING : Cannot resolve symlink '/opt/local/lib/libgtkglext-x11-1.0.0.dylib '
/!\ WARNING : Cannot resolve symlink '/opt/local/lib/libjasper.1.dylib '
/!\ WARNING : Cannot resolve symlink '/opt/local/lib/libz.1.dylib '
/!\ WARNING : Cannot resolve symlink '/usr/lib/libstdc++.6.dylib '

– Andy

@jdolan
Copy link
Collaborator

jdolan commented Jul 6, 2013

The gobs and gobs of warnings is normal. And yes, it does take nearly as long to bundle as it does to compile, because dylibbundler has to recursively find all of our dependencies down to the /System folder, copy them, and then rewrite them without breaking them.

Check the ports manual for how to force a recompile of a port. Frankly, it's not as easy as it should be. But it does work. Be sure the environment variable (export LDFLAGS=-headerpad_max_install_names) takes before you kick off the recompile.

@TTimo
Copy link
Owner

TTimo commented Jul 13, 2013

You can also switch to the latest port compiled out of the svn trunk code for the macports project. 2.2 has headerpad correctly configured by default. Worked for me.

@TTimo TTimo closed this as completed Jul 13, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants