#49932: Incompatible library version: libnetcdf.7.dylib requires version 9.0.0 or later, but libcurl.4.dylib provides version 8.0.0 --------------------------+-------------------------- Reporter: veit.helm@… | Owner: ryandesign@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: invalid | Keywords: Port: curl | --------------------------+-------------------------- Changes (by cal@…): * status: new => closed * resolution: => invalid Comment: Yes, if you fork process from a certain environment there is a high probability that they have `DYLD_LIBRARY_PATH` exported (because people assume `DYLD_LIBRARY_PATH` works similar to `LD_LIBRARY_PATH` on Linux – hint: it doesn't) and then run into this issue. You should file a bug with the providers of that commercial software and ask them to not rely on `DYLD_LIBRARY_PATH`. Even `DYLD_FALLBACK_LIBRARY_PATH` should be unnecessary on OS X, because libraries are referenced using absolute paths on OS X, which enables 3rd party commercial vendors to link against their own copies of libraries without relying on any `DYLD_*` variables. As you have already said, this is not a bug in MacPorts and I'm going to close this ticket. We may want to check our documentation for the usage of `env | grep DYLD` and replace them for 10.11 compatibility, though. -- Ticket URL: <https://trac.macports.org/ticket/49932#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X