#45305: bind9: opportunistically links with json-c but build fails when jsoncpp is active --------------------------+--------------------- Reporter: ryandesign@… | Owner: dluke@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Keywords: | Port: bind9 --------------------------+--------------------- If the jsoncpp and json-c ports are both installed and active, building bind9 fails with: {{{ :info:build In file included from app.c:40: :info:build In file included from ../include/isc/mem.h:27: :info:build In file included from ../include/isc/json.h:29: :info:build In file included from /opt/local/include/json/json.h:9: :info:build In file included from /opt/local/include/json/autolink.h:9: :info:build /opt/local/include/json/config.h:73:1: error: unknown type name 'namespace' :info:build namespace Json { :info:build ^ :info:build /opt/local/include/json/config.h:73:15: error: expected ';' after top level declarator :info:build namespace Json { :info:build ^ :info:build ; }}} If jsoncpp is active but json-c is not, configure fails with: {{{ checking for json library... yes checking for library containing json_object_new_int64... no configure: error: found libjson include but not library. }}} If json-c is active but jsoncpp is not active, bind9 builds successfully and links with the json-c library. If neither json-c nor jsoncpp are active, bind9 builds successfully, but without json support. I believe the problem relates to the fact that the json-c headers have recently changed location in order to not conflict with jsoncpp. bind9 may still be erroneously looking for json-c's headers in their old location. Also, bind9 either needs to declare a dependency on json-c, or not use it even if it is already installed. -- Ticket URL: <https://trac.macports.org/ticket/45305> MacPorts <http://www.macports.org/> Ports system for OS X