[issue15353] ld: library not found for -lpython3.3m because of wrong LDFLAGS_PYTHON

Ned Deily added the comment: Thanks for the report. The python-3.3.pc file is correct. It is a symlink to the python-3.3m.pc. What isn't correct is that OS X framework builds were not creating the proper libpython3.3m.{dylib,a} symlinks for use with python3.x-config and with pkg-config (if

[issue15353] ld: library not found for -lpython3.3m because of wrong LDFLAGS_PYTHON

Changes by Ned Deily : -- assignee: ronaldoussoren -> ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15353] ld: library not found for -lpython3.3m because of wrong LDFLAGS_PYTHON

Changes by Antoine Pitrou : -- nosy: +hynek, ned.deily ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue15353] ld: library not found for -lpython3.3m because of wrong LDFLAGS_PYTHON

New submission from Jerry Jacobs : Dear all, I'm using python in a application (sigrok.org) and want to ship it as a framework with a .app folder. I'm building python-3.3b1 from source to a .framework. It is correctly compiled and installed in the given directory. Only the python-3.3.pc is i