Open jonassmedegaard opened 3 years ago
I'd just disable the mongrel plugin then, not sure there's many users out there.
Turns out what fails is building in an environment where only libyajl headers are available.
What works is to install both libyajl and libjansson headers and configure the build to explicitly use json = yajl
(not json = yes
). Then uWSGI generally links against libyajl and only mongrel2 plugin links against libjansson.
Seems to be that this issue is solved by changing mongrel2 plugin to not only check for UWSGI_JSON
but also do a negated check for both UWSGI_JSON_YAJL
and UWSGI_JSON_YAJL_OLD
.
I recommend to also document that mongrel2 plugin requires libjansson and how it behaves (fails to build or silently disables certain communication) if switching to libuyajl.
Attempting to build uWSGI linked with libyajl instead of libjansson causes failure in plugin mongrel2:
...
Reason I wanted to switch JSON parse was this report of symbol leaks aused problems with applications linking (transitively) against both libjansson and libjson.