You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS: OS X 10.8.5
I was able to compile rust on 8-9-2013.
The problem seems to be twofold:
After upgrading the command line tools to xcode 5 (september '13) and executing
configure is stuck at: configure: CFG_CCACHE with xcrun running at about 90% CPU utilization. I killed it after about 10min- rerunning it doesn't change anything.
I then installed xcode462_cltools_10_86938259a and was able to run ./configure successfully. The compilation process progressed up until libuv and was stuck again with xcrun running at about 90% CPU utilization. I killed it after 50min.
In the end I was able to compile rust after doing
sudo xcode-select -switch /usr/bin
The problem seems to be caused by a misconfiguration, but still, xcrun shouldn't just block (infinitely(?)).
rust 0.8 (01313a1 2013-09-27 06:21:22 -0700)
The text was updated successfully, but these errors were encountered:
Fix to_string_in_format_args in parens
Fix suggestions like
```
print!("error: something failed at {}", (Location::caller().to_string()));
```
where the parenthesis enclose some portion of the value.
Fixesrust-lang#9540
changelog: [`to_string_in_format_args`]: fix incorrect fix when value is enclosed in parenthesis
OS: OS X 10.8.5
I was able to compile rust on 8-9-2013.
The problem seems to be twofold:
After upgrading the command line tools to xcode 5 (september '13) and executing
configure is stuck at: configure: CFG_CCACHE with xcrun running at about 90% CPU utilization. I killed it after about 10min- rerunning it doesn't change anything.
I then installed xcode462_cltools_10_86938259a and was able to run ./configure successfully. The compilation process progressed up until libuv and was stuck again with xcrun running at about 90% CPU utilization. I killed it after 50min.
In the end I was able to compile rust after doing
The problem seems to be caused by a misconfiguration, but still, xcrun shouldn't just block (infinitely(?)).
The text was updated successfully, but these errors were encountered: