#41271: libkml @1.2.0_1 conflicts with uriparser @0.7.2 -------------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: fixed | Keywords: Port: libkml uriparser | -------------------------------+-------------------------------- Changes (by ryandesign@…): * cc: ed@… (removed) * status: new => closed * resolution: => fixed Comment: Fixed in r136039. libkml 1.2.0 always builds and installs its own copy of liburiparser; there is no configure argument to let it use an already-installed copy. A [https://code.google.com/p/libkml/issues/detail?id=50 bug report] was filed and a patch was provided to enhance the configure script to provide this, but it was never committed to the repository; the project has not been updated since 2010. Several developers have forked it to github but none have declared themselves to be authoritative and released new versions. To use the patch, I had to regenerate the configure script. This uncovered [https://code.google.com/p/libkml/issues/detail?id=186 additional] [https://code.google.com/p/libkml/issues/detail?id=190 bugs] in the configure script when used with recent versions of autoconf, for which there were more bugs and uncommitted patches provided. There is an additional problem in the configure script or Makefiles when used with recent versions of autotools which causes the build to fail when dependency tracking is on, which is the default when not building universal. No patch was provided for this so I just disabled dependency tracking. The build system relies on liburiparser's .la file existing, which MacPorts deletes by default on OS X 10.9 Mavericks and later, so I had to modify uriparser not to delete its .la file. -- Ticket URL: <https://trac.macports.org/ticket/41271#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X