[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 qwertjadaml@…):

 OK, thank you for your response and clarification.

 > Jeremy is just curt sometimes. Don’t take stuff so personally.

 Nothing personal, I'm just ''really'' tired to see the seriously unhelpful
 error message “user error”—that describes more about the nature of the
 user rather than the error and doesn't even help how to troubleshoot
 it—seen many times on early Windows versions and programs. (Come to think
 of it, I barely met it on recent versions.) But (mostly to self) lets get
 over that.

 > 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.

 I wasn't around here since recently, so I'm not quite aware of this, but I
 roughly can imagine how it goes.

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

 Funny it may be, but I tried my best to take care both of those before I
 bother to install anything with MacPorts, and I thought everything is OK
 with that.

 To my own defence, Apple just have slightly changed how Xcode handles
 download-able content, and in their download section there was no command
 line tools as an option, but later figured that ‘cc’ still somehow works,
 as well as there was an option to select the compiler, so I figured I'm
 OK. Also I ''had'' the SDK on my system, but it wasn't “staged” in their
 proper place to be seen my MacPorts build mechanism, as I've found out
 today. (It was under /Application/Xcode.app/…)

 And just after I came back here to report this, I've tried xcode-select as
 larry suggested, and the apple updater immediately popped up that this
 should be installed. (Which is strange to me, since I've just read it's
 man page before I run it… or I misunderstood something, and additional
 programs were installed.)

 > 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.

 That would be great, especially that Xcode just changed how it is installs
 the command line tools that I've just pointed out, that it isn't clear to
 me how to do that now. (in fact, I'm so confused now, that I'm not sure if
 I did it at all. Because Apple wants it simple…)

 It would also be nice, if Google could point to a page that clarifies both
 what you encounter with every Mac upgrade, and what just I've
 encountered—if such page exists that is.

 Thanks for the help, and I hope that my encounter helps a tiny-bit more in
 the future.

 Ps.:
 I have a feeling, that you may encounter such bug-report more than with
 any other upgrade before with this version of Xcode.

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