Created attachment 176691 [details] patch If libzmq is installed in an alternate location (by changing LOCALBASE), py-pyzmq will fail to find it and builds the included zmq instead. The existing Makefile patches setup.cfg, but the behavior must have changed at one point because this no longer seems to have an effect. Instead, we can use --zmq=<path>. The attached patch does this.
Created attachment 176907 [details] update to 16.0.1 Hi, Thanks for the patch. I've prepared an update to 16.0.1 and included your change as well. I've attached a patch that does the following: - update to 16.0.1 - use standard test target and add TEST_DEPENDS - fix detecting zmq in non-default LOCALBASE PS It looks like configuration *is* supported through setup.cfg, and it's controlled by value of the "zmq_prefix" option. But configure switch is easier than sedding files. Also, it looks like lib dirs and include dirs are set based on zmq_prefix, so there is no need to define those, so I dropped the part with setup.cfg creation. Does this look reasonable to you?
Hi Roman, Yep - this makes perfect sense.
A commit references this bug: Author: novel Date: Sat Nov 12 13:08:14 UTC 2016 New revision: 425949 URL: https://svnweb.freebsd.org/changeset/ports/425949 Log: net/py-pyzmq: update to 16.0.1 - update to 16.0.1 - rename regression-test target to do-test and add TEST_DEPENDS - fix detecting zmq in non-default LOCALBASE [1] PR: 214274 [1] Submitted by: jhujhiti@adjectivism.org [1] Changes: head/net/py-pyzmq/Makefile head/net/py-pyzmq/distinfo
Committed, thanks!