Re: [MacPorts] #52634: nodejs4 build failure — type_traits not found when targetting mac OS 10.8 (was: -snodejs4 build failure — type_traits not found when targetting mac OS 10.8)

[MacPorts]

#52634: nodejs4 build failure — type_traits not found when targetting mac OS 10.8
------------------------+-------------------------
  Reporter:  william@…  |      Owner:  ciserlohn@…
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.3.4
Resolution:             |   Keywords:
      Port:  nodejs4    |
------------------------+-------------------------
Changes (by larryv@…):

 * owner:  macports-tickets@… => ciserlohn@…
 * cc: ciserlohn@… (removed)


Comment:

 Replying to [ticket:52634 william@…]:
 > Problem arises due to the presence of the following lines in my
 macports.conf:
 >
 > {{{
 > macosx_deployment_target 10.8
 > configure.macosx_deployment_target 10.8
 > cxx_stdlib libc++
 > configure.cxx_stdlib libc++
 > cxxflags -std=c++14
 > configure.cxxflags -std=c++14
 > }}}

 The only valid settings here are `macosx_deployment_target` and
 `cxx_stdlib`. MacPorts does not recognize the others.

 > The solution, then, is to add the -stdlib=libc++ argument to build
 > lines unconditionally (it does no harm on systems which already have
 > that as the default). I'm having a nose around to see how that is
 > achieved, since the build system here clearly ignores the cxx_stdlib
 > variables set in macports.conf …

 `CXXFLAGS` already contains `-stdlib=libc++`. So the problem is that the
 build system is not respecting that.

 Many if not all of the compiler invocations use `-std=gnu++0x`. Does this
 software require C++11 support? If so, the portfile ought to take this
 into account.

-- 
Ticket URL: <https://trac.macports.org/ticket/52634#comment:1>
MacPorts <https://www.macports.org/>
Ports system for the Mac operating system