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

Symbol not found: _PyBool_Type #2085

Closed
lakenen opened this issue Feb 23, 2015 · 13 comments
Closed

Symbol not found: _PyBool_Type #2085

lakenen opened this issue Feb 23, 2015 · 13 comments

Comments

@lakenen
Copy link

lakenen commented Feb 23, 2015

I get the following when I run fontforge on the command line (installed from source @ master):

dyld: Symbol not found: _PyBool_Type
  Referenced from: /usr/local/lib/libfontforge.2.dylib
  Expected in: flat namespace
 in /usr/local/lib/libfontforge.2.dylib
Trace/BPT trap: 5

On OS X 10.9.5, configured with this command to work with homebrew:

PATH="/usr/local/Cellar/gettext/0.19.4/bin/:${PATH}" \
  CFLAGS="-I./libltdl" \
  LIBPNG_CFLAGS="-I/usr/local/lib" \
  LIBPNG_LIBS="-L/usr/local/lib" \
  ZLIB_CFLAGS="-I/usr/lib" \
  ZLIB_LIBS="-L/usr/lib" \
  PYTHON_CFLAGS="-I/usr/local/Cellar/python/2.7.9/Frameworks/Python.framework/Versions/2.7/include/python2.7" \
  PYTHON_LIBS="-L/usr/local/Cellar/python/2.7.9/Frameworks/Python.framework/Versions/2.7/lib/python2.7/config" \
  ./configure --with-pythonbinary=/usr/local/bin/python
@lakenen
Copy link
Author

lakenen commented Feb 23, 2015

For what it's worth, the python bindings work. I just get that error when I run fontforge on the command line.

@davelab6 davelab6 mentioned this issue Feb 23, 2015
9 tasks
@davelab6
Copy link
Member

@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 brew install fontforge --with-x11 --HEAD

@lakenen
Copy link
Author

lakenen commented Feb 27, 2015

I built from source with the configure command above, then make

@davelab6
Copy link
Member

davelab6 commented Feb 27, 2015 via email

@lakenen
Copy link
Author

lakenen commented Feb 27, 2015

It works fine from homebrew. The issue is with installing from source.

@davelab6 davelab6 added this to the 2015-03 Release milestone Feb 28, 2015
@davelab6
Copy link
Member

I'm curious! Why would you do that? :) If it works in Homebrew, why not just use Homebrew?

@lakenen
Copy link
Author

lakenen commented Feb 28, 2015

I'm developing against fontforge with the python bindings, and I occasionally run into bugs like this: #2086 :)

@davelab6
Copy link
Member

davelab6 commented Feb 28, 2015 via email

@lakenen
Copy link
Author

lakenen commented Feb 28, 2015

Reason being I can apply the patch locally even if it's not merged.

@davelab6
Copy link
Member

davelab6 commented Feb 28, 2015 via email

@frank-trampe
Copy link
Contributor

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.

@lakenen
Copy link
Author

lakenen commented Mar 2, 2015

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?

@jtanx
Copy link
Contributor

jtanx commented Jun 11, 2019

I use a variant of

PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/local/opt/libffi/lib/pkgconfig  ./configure --enable-gdk=gdk3

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.

@jtanx jtanx closed this as completed Jun 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants