[MacPorts] #57513: bazel @0.18.0: error: no type named 'unique_ptr' in namespace 'std'

MacPorts noreply at macports.org
Mon Nov 5 18:39:14 UTC 2018


#57513: bazel @0.18.0: error: no type named 'unique_ptr' in namespace 'std'
-------------------------+--------------------------
  Reporter:  ryandesign  |      Owner:  RootFunction
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:
Resolution:              |   Keywords:
      Port:  bazel       |
-------------------------+--------------------------

Comment (by cjones051073):

 bazel probably does everything differently to any other build system you
 might have looked at.

 It *really* wants to control everything itself, including the compiler
 selection, build options and dependencies. Its very very tough to get it
 to change its mind on these things.

 One thing I did try is I pushed an update to to forcibly (via a reinplace)
 change all c++0x in the source to c++11. That got things a little further
 on 10.8 bit it still fails.

 To be frank, it was enough of an effort to get things build down to 10.9.
 I'm happy with that, and if someone else comes along who has an interest
 in fixing bazel in older systems, they are more than welcome to try.  My
 interest in bazel only stems from the fact I needed it to provide a py-
 tensorflow port that builds from source itself.

-- 
Ticket URL: <https://trac.macports.org/ticket/57513#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list