[MacPorts] #41718: dsniff ports has issues.

[MacPorts]

#41718: dsniff ports has issues.
-----------------------+-----------------------------
  Reporter:  alfred@…  |      Owner:  cal@…
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:  MacPorts Future
 Component:  ports     |    Version:  2.2.1
Resolution:            |   Keywords:
      Port:            |
-----------------------+-----------------------------

Comment (by cal@…):

 Unfortunately MacPorts just assumes you have the Command Line Tools
 installed and does not track which ports actually use them. Since (until
 10.9) the Command Line Tools provided `/usr/bin/clang` that wasn't an
 issue, though – builds would just fail immediately without them.

 Since 10.9 the shims installed as `/usr/bin/clang` and similar tools no
 longer tell you to install the Command Line Tools but fall back to using
 compilers from Xcode, if you have that installed. Unfortunately, that
 breaks in subtle ways, such as this one. Note that "depends on Xcode"
 would actually not be correct, because it "depends on Xcode CLT" in this
 case, and we should really distinguish both those cases because those
 packages can be installed separately.

 Tracking these requirements is a good idea but hasn't been done yet and
 would require a lot of work at the moment. Fortunately, a feature I've
 been working on called trace mode to be released with the next major
 release should make getting this right a lot simpler.

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