This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Jerry.Jacobs
Recipients Jerry.Jacobs, ronaldoussoren
Date 2012-07-14.20:30:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1342297831.17.0.252581659185.issue15353@psf.upfronthosting.co.za>
In-reply-to
Content
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 incorrect because it has not the name python-3.3m.pc and includes the following library entries: Libs: -L${libdir} -lpython3.3m

So this results in:
ld: library not found for -lpython3.3m
because of the deployment of the wrong .pc Libs directive:
build/decoders/nunchuk/Makefile
127:CPPFLAGS_PYTHON = -I/Users/jerry/Sigrok/Python.framework/Versions/3.3/include/python3.3m -I/Users/jerry/Sigrok/Python.framework/Versions/3.3/include/python3.3m
159:LDFLAGS_PYTHON = -L/Users/jerry/Sigrok/Python.framework/Versions/3.3/lib/python3.3/config-3.3m -ldl -framework CoreFoundation -lpython3.3m -framework CoreFoundation Python.framework/Versions/3.3/Python
187:PYTHON3_CONFIG = python3.3m-config

Kind regards,
Jerry
History
Date User Action Args
2012-07-14 20:30:31Jerry.Jacobssetrecipients: + Jerry.Jacobs, ronaldoussoren
2012-07-14 20:30:31Jerry.Jacobssetmessageid: <1342297831.17.0.252581659185.issue15353@psf.upfronthosting.co.za>
2012-07-14 20:30:30Jerry.Jacobslinkissue15353 messages
2012-07-14 20:30:30Jerry.Jacobscreate