[MacPorts] #54176: boost assumes libc++ is only used by clang

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[MacPorts] #54176: boost assumes libc++ is only used by clang

MacPorts
#54176: boost assumes libc++ is only used by clang
-------------------------+-------------------
 Reporter:  RJVB         |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  Normal       |  Milestone:
Component:  ports        |    Version:
 Keywords:  haspatch     |       Port:  boost
-------------------------+-------------------
 While testing the idea of using libc++ while building C++ code with G++ I
 ran into (amost) exactly the errors shown here :
 http://stackoverflow.com/questions/41050942/clang-modules-interaction-
 with-std-iterator-and-boost-move-iterator-hpp/43983903

 In this case the errors were not caused by libc++ but by the simple fact
 that in a few locations, boost assumes that libc++ is only used with
 clang.

 After fixing those presumptions with the attached patch I was able to
 build both boost and digiKam5 (which uses Boost and is a good test for any
 C++ compiler).

--
Ticket URL: <https://trac.macports.org/ticket/54176>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #54176: boost assumes libc++ is only used by clang

MacPorts
#54176: boost assumes libc++ is only used by clang
--------------------------+----------------------
  Reporter:  RJVB         |      Owner:
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:  haspatch
      Port:  boost        |
--------------------------+----------------------
Changes (by RJVB):

 * Attachment "patch-libcpp-everywhere.diff" added.


--
Ticket URL: <https://trac.macports.org/ticket/54176>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #54176: boost assumes libc++ is only used by clang

MacPorts
In reply to this post by MacPorts
#54176: boost assumes libc++ is only used by clang
--------------------------+------------------------
  Reporter:  RJVB         |      Owner:  ryandesign
      Type:  enhancement  |     Status:  assigned
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:  haspatch
      Port:  boost        |
--------------------------+------------------------
Changes (by mf2k):

 * cc: ryandesign (removed)
 * owner:   => ryandesign
 * status:  new => assigned


--
Ticket URL: <https://trac.macports.org/ticket/54176#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #54176: boost assumes libc++ is only used by clang

MacPorts
In reply to this post by MacPorts
#54176: boost assumes libc++ is only used by clang
--------------------------+------------------------
  Reporter:  RJVB         |      Owner:  ryandesign
      Type:  enhancement  |     Status:  assigned
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:  haspatch
      Port:  boost        |
--------------------------+------------------------

Comment (by neverpanic):

 I think this should go to boost upstream.

--
Ticket URL: <https://trac.macports.org/ticket/54176#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS
Reply | Threaded
Open this post in threaded view
|

Re: [MacPorts] #54176: boost assumes libc++ is only used by clang

MacPorts
In reply to this post by MacPorts
#54176: boost assumes libc++ is only used by clang
--------------------------+------------------------
  Reporter:  RJVB         |      Owner:  ryandesign
      Type:  enhancement  |     Status:  assigned
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:  haspatch
      Port:  boost        |
--------------------------+------------------------

Comment (by RJVB):

 it probably should, but in that case we should probably first update the
 port

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