Re: [MacPorts] #46120: dcmtk @3.6.1_20140617_1: error: no matching function for call to ‘test::test()’

[MacPorts]

#46120: dcmtk @3.6.1_20140617_1: error: no matching function for call to
‘test::test()’
---------------------------+------------------------
  Reporter:  ryandesign@…  |      Owner:  eborisch@…
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:  2.3.3
Resolution:                |   Keywords:
      Port:  dcmtk         |
---------------------------+------------------------

Comment (by ryandesign@…):

 Replying to [comment:6 larryv@…]:
 > Replying to [comment:5 ryandesign@…]:
 > > I know that using MacPorts llvm 3.5 and later means forcing the use of
 > > libc++, which can be problematic on OS X 10.8 and earlier. I'm not
 > > sure if using MacPorts clang 3.5 and later has the same effect.
 >
 > Since `clang-3.5` requires `llvm-3.5`, it requires `libcxx`
 transitively. I wouldn’t be surprised if it also uses libc++ directly.

 I understand that clang uses llvm and links with its libraries, and that
 since llvm-3.5 requires libc++, that means clang-3.5 requires libc++. But
 clang is a compiler. Software compiled using that compiler does not
 automatically use llvm nor link with its libraries, just by virtue of
 having used that compiler. Therefore, it does not follow that software
 compiled with clang-3.5 need necessarily itself require libc++.

-- 
Ticket URL: <https://trac.macports.org/ticket/46120#comment:12>
MacPorts <https://www.macports.org/>
Ports system for OS X