[MacPorts] #45380: nodejs, nodejs-devel: build fails with 12, 000 lines of make errors
#45380: nodejs, nodejs-devel: build fails with 12,000 lines of make errors --------------------------+---------------------------------- Reporter: ryandesign@… | Owner: ciserlohn@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Keywords: | Port: nodejs, nodejs-devel --------------------------+---------------------------------- This is a new one for me. nodejs and nodejs-devel are failing to build with 12,000 lines of `make` errors in the log that I don't understand. I had previously been able to install nodejs-devel @0.11.14 on September 25, 2014 but can't today; OS and Xcode and port updates have of course happened since then. I had not tried to install nodejs until today. This is on OS X 10.10 Yosemite beta 6. Same result with Xcode 6.0.1 and Xcode 6.1 GM 2. -- Ticket URL: <https://trac.macports.org/ticket/45380> MacPorts <http://www.macports.org/> Ports system for OS X
#45380: nodejs, nodejs-devel: build fails with 12,000 lines of make errors -----------------------------------+------------------------- Reporter: ryandesign@… | Owner: ciserlohn@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: haspatch Port: nodejs, nodejs-devel | -----------------------------------+------------------------- Changes (by ryandesign@…): * keywords: => haspatch Comment: I learned that the output I'm seeing is `make` debug output, enabled by the `-d` flag. I noticed that the nodejs portfile sets environment variables in such a way that it assumes the values do not contain spaces. I am running the trunk version of MacPorts base where `${configure.cxxflags}` does contain a space, since it now includes the `-stdlib=libc++` flag, which, if each character is interpreted as a flag, as `make` apparently does, would be equivalent to `-s -t -d -l -i -b`, etc. Attached is a patch to fix this. With MacPorts base from trunk, nodejs is now being build with the correct C++ library. It now fails with this message: {{{ clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later) }}} I am of course running OS X 10.7 or later, but the build is specifying `-mmacosx-version-min=10.5`, which is incompatible. This should be changed to use `${macosx_deployment_target}` instead of assuming it should be `10.5`. -- Ticket URL: <https://trac.macports.org/ticket/45380#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#45380: nodejs, nodejs-devel: build fails with 12,000 lines of make errors -----------------------------------+------------------------- Reporter: ryandesign@… | Owner: ciserlohn@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: | Keywords: haspatch Port: nodejs, nodejs-devel | -----------------------------------+------------------------- Comment (by ryandesign@…): Simply removing the `MACOSX_DEPLOYMENT_TARGET` setting from common.gypi allows the MacPorts default value to be used. The attached patch allows the build to succeed. I'm increasing the revision because on Mavericks and later this change will cause libc++ to be used instead of libstdc++. -- Ticket URL: <https://trac.macports.org/ticket/45380#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#45380: nodejs, nodejs-devel: build fails with 12,000 lines of make errors -----------------------------------+------------------------- Reporter: ryandesign@… | Owner: ciserlohn@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.99 Resolution: fixed | Keywords: haspatch Port: nodejs, nodejs-devel | -----------------------------------+------------------------- Changes (by ciserlohn@…): * status: new => closed * resolution: => fixed Comment: Thanks for the patch. Applied in r126814. -- Ticket URL: <https://trac.macports.org/ticket/45380#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts