Which will ensure that libcrypto is loaded when you NSLinkModule...
What is likely happening here is that when you first try to lookup the
symbol in the module, dyld tries to bind the undefined symbols, and
because the bundle was not linked against libcrypto, it can't find
some of them.
This is actually one the things I have tried. It makes no difference.
otool -L also shows that the linking of crypto from the first line is
happily carried through into the final product.
You should be calling NSLinkEditError if nssymbol is null to check why.
Thanks, I'll try this.
Sean
_______________________________________________
unix-porting mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/unix-porting
Do not post admin requests to the list. They will be ignored.
