[MacPorts] #49696: cmake-3.4.0 - build succeeded on MacBook, failed on iMac
#49696: cmake-3.4.0 - build succeeded on MacBook, failed on iMac --------------------+-------------------------------- Reporter: bert@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: cmake --------------------+-------------------------------- cmake-3.4.0 - build succeeded on my MacBook, but failed on my iMac -- Ticket URL: <https://trac.macports.org/ticket/49696> MacPorts <https://www.macports.org/> Ports system for OS X
#49696: cmake-3.4.0 - build succeeded on MacBook, failed on iMac ---------------------+-------------------------------- Reporter: bert@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: cmake | ---------------------+-------------------------------- Comment (by macports@…): You have a version of cURL in /Library/Frameworks/libcurl.framework that does not contain 64-bit symbols. The cmake build script is picking it up rather than the MacPorts version in /opt/local, which causes the build to fail. Please remove the conflicting framework and try again. -- Ticket URL: <https://trac.macports.org/ticket/49696#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#49696: cmake @3.4.0 build fails if /Library/Frameworks/libcurl.framework exists ---------------------+------------------------- Reporter: bert@… | Owner: michaelld@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: cmake | ---------------------+------------------------- Changes (by ryandesign@…): * cc: css@…, ryandesign@… (added) * owner: macports-tickets@… => michaelld@… * priority: High => Normal Comment: That's true. See wiki:FAQ#libraryframeworks. However, this problem comes up so frequently that I would like to see it fixed in the cmake port. It should be possible, and is a best practice, to inform the cmake build system which libcurl (and libz and libbz2 and libarchive and so on) we would like it to use, rather than letting it guess (wrongly). -- Ticket URL: <https://trac.macports.org/ticket/49696#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#49696: cmake @3.4.0 build fails if /Library/Frameworks/libcurl.framework exists ---------------------+------------------------- Reporter: bert@… | Owner: michaelld@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: cmake | ---------------------+------------------------- Comment (by michaelld@…): I agree with Ryan that cmake finding dependencies outside of $prefix has been a PITA before & should just be fixed if we can reasonably do so. Thus, in r143049 I tweaked the settings in the macports.cmake settings file & hopefully these will take care of this issue for all dependencies. Can someone with the external Curl installed do a selfupdate & then test installing cmake to verify that it now works? -- Ticket URL: <https://trac.macports.org/ticket/49696#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts