-
Notifications
You must be signed in to change notification settings - Fork 686
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
dyld: Library not loaded #1837
Comments
cc @monkeyiq |
It is interesting that it is finding and linking to czmq for you. Otherwise it wouldn't have the failing reference. So it seems that some of the pkg-config stuff is working, it's just not linking the zmq too by the looks. What do you have in /opt/local/lib by way of zmq?
For reference this is what I have on my main build machine:
In the top fontforge build directory:
The relevant section of config.log:
|
/usr/local/lib for me 😉. I use Homebrew rather than MacPorts.
And:
|
I assume that when you 'grep LIBZMQ Makefile' after a configure then you only see the link line for czmq and no -lzmq (and matching -L to your zeromq/lib subdir)? |
OK, switching over to osx 10.8 using brew I have:
If I also see the link dependencies of fontforge on that brew based machine I get the following:
Maybe there are some differences between our machines there. I will also check if current master is ok to build on that machine. |
|
|
is the above for a fontforge that is meant to have collab enabled? the binary doesn't seem to want czmq at all, so the fontforge --version should work for it? |
No, I had to turn collab off to get it to launch at all after compile. I'll turn it back on now for testing and check again. |
I am now also recompiling head on that machine using
|
Alright, with collab turned on:
|
And when you run "fontforge --version" you still get dyld: Library not loaded: /usr/local/lib/libzmq.3.dylib? I assume that "otool -L /usr/local/lib/libczmq.1.dylib " shows that czmq wants to link to that libzmq.3.dylib file instead of the libzmq.4.dylib that the fontforge binary is after? |
Oh. Okay, this is curious. Now it works. I did a complete removal and re-installation of the two zmq dependencies, so maybe that was the issue 😕
|
For reference I get the following otool for fontforge...
|
Did Fontforge do anything in the last change that would require the two dependencies to be built fresh rather than used already on the system? This is odd. |
I haven't changed the brew file for ages. It seemed you might have had a dangling libzmq.3 link somewhere. I notice your /usr/local/opt/zeromq/lib listing above only had libzmq.4.dylib. My machine only has libzmq.3.dylib, but for me nothing wants libzmq.4.dylib instead. Perhaps if I update the zmq dep on the machine then it will move over to libzmq.4.dylib. $ ls -l /usr/local/opt/zeromq/lib |
Yeah, It looks possibly like the Now I've recompiled the two zmq dependencies that |
At least we seem to have solved the problem, from fontforge's perspective ;) I knew having that brew machine available was the right choice ;-) |
Alright, I've made the necessary changes locally to fix this. Just waiting on feedback on the UUID issue and then I'll petition Homebrew to accept the changes. Closing this in the hope of not having to reopen it later. Thanks for the help 😃 |
Cool, let me know if you need any support on getting homebrew to accept the changes. I don't have any privilege there, but if I can help even in a minor way to make fontforge easier to build I'm all for it! |
Some fixes for the Fontforge, pending the next imminent stable release. Also bumping czmq and zeromq following a discussion [on this](fontforge/fontforge#1837) this morning, during which I stumbled across a fix by removing the two and reinstalling them afresh, so I’m recommending we do that for everyone given the two libraries are tiny and it’ll flush out any configuration or bottle issues that could be lingering.
just use ln ln -s /usr/local/opt/zeromq/lib/libzmq.5.dylib /usr/local/lib/libczmq.3.dylib |
On OS X:
The czmq we're using is version 2.2.0 which should be sufficient according to the build documentation, but Fontforge seems to be ignoring the pkg-config file and refusing to see this dependency is present and consequently when attempting to load Fontforge from the command-line we see the dylib failure displayed above.
Any ideas? For now, I may just turn the collab dependencies into optional dependencies for Homebrew and change that when we fix this little issue.
The text was updated successfully, but these errors were encountered: