[MacPorts] #41000: Failed to build xorg-libAppleWM on Mavericks

[MacPorts]

#41000: Failed to build xorg-libAppleWM on Mavericks
------------------------------+------------------------
  Reporter:  markus@…         |      Owner:  jeremyhu@…
      Type:  defect           |     Status:  closed
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.2.1
Resolution:  invalid          |   Keywords:
      Port:  xorg-libAppleWM  |
------------------------------+------------------------

Comment (by jeremyhu@…):

 Replying to [comment:3 qwertjadaml@…]:
 > Dear jeremyhu at macports.org,
 >
 > I took the strength to be kind despite your “User error” statement—which
 I try my best not to note it further on—and try to take my time to explain
 it to you, that the issue clearly exists and valid, as in the compiler
 cannot find the “HIServices/Processes.h” file, and that fact is anything
 ''but'' a user error. (Unless you referring yourself.)

 I apologize for being quick in response to this.  With every OS release,
 MacPorts get a bunch of reports like this because users do not follow the
 proper upgrade procedures.

 In your case, the missing file is not our fault and does not warrant a
 bug.

 > Apple seems to quite freely changes their API, so it wouldn't surprise
 me, if something has changed regarding header file or library locations or
 rearrangement. I couldn't find the header file, however I could find the
 HIServices.framework.

 You have not installed the SDK which is why the file is missing.

 > Your next sentence however implies that either the necessary
 dependencies are not installed, which is absurd, since MacPort installs
 all required port marked as depending port for that particular port;
 ''or'' you're asking the user to install the MacPorts Dependencies command
 line tools, which seems to be non-existent.

 Yes, you must install Xcode and the command line tools.

 > Do you think you can take a look in to it what is the issue is, or
 you're not convinced by all these that it is actually an issue here?

 We know what the issue is.  You have not installed the SDK.  Because of
 the slew of reports we get about this issue every release, we have been
 talking on macports-dev for the past few weeks about this and are also
 looking into detecting this for you and referring users to the FAQ instead
 of fending off hundreds of invalid bug reports.

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