-
Notifications
You must be signed in to change notification settings - Fork 13.3k
can't build head on my os x 10.8 machine #10941
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
the key piece seems to be
|
I would recommend blowing away your local LLVM build tree and rebuilding LLVM. I've seen this often happen when LLVM gets out of date. |
I'll try that next. But i literally only did the clone < 1 hour ago! How could the llvm be out of date already? |
Hm, if this is a fresh build, then that's a little disturbing. This normally happens when old checkouts are updated with a new LLVM and things get out of sync. In your case, an LLVM rebuild may not be sufficient (sorry I should have read the initial report a little more closely). |
another important point is that i did i'm going to try |
i believe |
ok, well, i'm going to just clone a fresh tree. Just tried building again and got
i'm confused by the
because theres no
on my computer.. |
I did a completely fresh clone, and got
|
I've a theory that the issue is that i'm using gcc rather than clang. (specifically i'm using gcc 4.8) I'll try using and if that fails, I'll try to use the rust i've got installed locally as the boostrap one instead |
still getting this problem |
heres the output of my most recent configure run, where the associated build is currently in progress build setup done as follow:
nb, prior build attempts have been variations of
|
so |
failed again. same error as before. now i'm testing will try some more ideas. This is weird |
current theory: cc points to xcode 5 clang, but gcc points to gcc 4.8. |
solution:
this can be determined by
though this could also use the |
closing this ticket, will open another one for checking for version compat |
[`no_effect`]: Suggest adding `return` if applicable Closes rust-lang#10941 Unfortunately doesn't catch anything complex as `no_effect` already wouldn't, but I'm fine with that (it catches `ControlFlow` at least :D) changelog: [`no_effect`]: Suggest adding `return` if statement has same type as function's return type and is the last statement in a block
I recently installed rust head a few days ago, and today I did a clone into a directory so i could peruse rustc source. I just tried to build that clone today, at commit 1b12dca and the install fails.
heres the relevant build log
nb: i have xcode 5 installed, but the gcc in my path is gcc 4.8.
The text was updated successfully, but these errors were encountered: