#40809 closed defect (worksforme)
llvm-gcc42 fails to compile on OS X 10.9
| Reported by: | PerMildner | Owned by: | erickt@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.0 |
| Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia) | |
| Port: | llvm-gcc42 |
Description
Attachments (1)
Change History (10)
Changed 11 years ago by PerMildner
comment:1 Changed 11 years ago by skymoo (Adam Mercer)
comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
The log says:
:info:build The directory that should contain system headers does not exist: :info:build /usr/include
Did you install the command line tools after installing Xcode?
comment:3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | jeremyhu@… added |
|---|---|
| Owner: | changed from macports-tickets@… to erickt@… |
comment:4 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Works for me. Mavericks is still under NDA. Please followup via email.
comment:5 follow-up: 6 Changed 11 years ago by PerMildner
About comment:2, publicly available information (e.g. here) indicates that XCode on Mavericks no longer installs /usr/include/.
Public (non-NDA) information from Apple, e.g. XCode What's New, says that the developer tools in Mavericks installs on-demand, i.e. there is no longer a separate step to "install the command line tools".
Perhaps the the success in comment:4 comes from having /usr/include/ installed by some previous version of OS X or XCode?
comment:6 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Replying to Per.Mildner@…:
About comment:2, publicly available information (e.g. here) indicates that XCode on Mavericks no longer installs /usr/include/.
Just because someone else violated the NDA does not mean that you are authorized to propagate such data. Nor does it mean that such data is accurate.
Public (non-NDA) information from Apple, e.g. XCode What's New, says that the developer tools in Mavericks installs on-demand, i.e. there is no longer a separate step to "install the command line tools".
I don't see where you see that.
Perhaps the the success in comment:4 comes from having /usr/include/ installed by some previous version of OS X or XCode?
No.
As mentioned, please take this to email if you require clarification.
comment:7 follow-up: 8 Changed 11 years ago by PerMildner
OS X 10.9 Mavericks and XCode 5.0.1 are public now, so NDA no longer applies.
The automatic install of command line tools performed by XCode 5.0.1 on first launch does not create the /usr/include/ directory and there is no longer an explicit option within XCode for installing the command line tools.
Unlike to automatic installation performed by XCode 5.0.1, the new xcode-select --install option will install command line tools and /usr/include/.
Also, if XCode has not been run, running something like cc --version will offer to install the command line tools which will also create /usr/include/.
In summary, the automatic install of command line tools performed by XCode 5.0.1 on first launch is incomplete.
comment:8 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
Replying to Per.Mildner@…:
OS X 10.9 Mavericks and XCode 5.0.1 are public now, so NDA no longer applies.
The automatic install of command line tools performed by XCode 5.0.1 on first launch does not create the /usr/include/ directory and there is no longer an explicit option within XCode for installing the command line tools.
I believe it should.
In summary, the automatic install of command line tools performed by XCode 5.0.1 on first launch is incomplete.
Please file a radar at http://bugreport.apple.com about this.
It built fine for me: