[MacPorts] #57576: llvm 8+ usability

MacPorts noreply at macports.org
Wed Apr 29 20:19:56 UTC 2020

#57576: llvm 8+ usability
  Reporter:  RJVB         |      Owner:  (none)
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  llvm-devel   |

Comment (by RJVB):

 Replying to [comment:5 RJVB]:
 > I think each clang version does use its own C++ headers on Linux, so
 I'll kick some tyres there to see what happens.

 Apparently it doesn't, but it does use the C++1x headers from the libc++
 install (/usr/include/c++/v1). On first glance I don't notice any issues,
 but I think there was no actual passing along of relevant data structures
 between the different translation units. I'm now rebuilding a host app
 with `clang++-5.0 -stdlib=libc++` and one of its more complex plugins with
 `clang++-8 -stdlib=libc++`, if that doesn't trip any of the more obvious
 (potential) taboos I don't know what would...

 Or, the quote above only actually pertains to libc++ 8 and up, regardless
 of the clang/llvm version with which it is used. In that case my tyre
 kicking is pointless because everything I have built with `clang++
 -stdlib=libc++` must have been (re)built against libc++ 8.0.0 already...

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

More information about the macports-tickets mailing list