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
Symbol not found: _PyBool_Type #2085
Comments
For what it's worth, the python bindings work. I just get that error when I run fontforge on the command line. |
@lakenen how did you build it? I tried on a clean install with homebrew and its ok... both with last release and head. I just |
I built from source with the configure command above, then |
no homebrew?
|
It works fine from homebrew. The issue is with installing from source. |
I'm curious! Why would you do that? :) If it works in Homebrew, why not just use Homebrew? |
I'm developing against fontforge with the python bindings, and I occasionally run into bugs like this: #2086 :) |
Okay :) I don't understand the aversion to homebrew in this case though :)
|
Reason being I can apply the patch locally even if it's not merged. |
apply patch to your fork of ff and update the recipe tobpoibt head to you
repo?
|
It's possible to have Homebrew build something that isn't in the main Homebrew tree. I will follow up when I'm back at the office on Monday. |
FWIW, I'd prefer to be able to build from source without homebrew. Is there something wrong with the way I've configured the build? |
I use a variant of
Which works for me. Travis also builds using homebrew - https://github.com/fontforge/fontforge/blob/master/.travis.yml Reopen if you're still having this issue. |
I get the following when I run
fontforge
on the command line (installed from source @ master):On OS X 10.9.5, configured with this command to work with homebrew:
The text was updated successfully, but these errors were encountered: